Exception - Resolving timed out after 5515 milliseconds

Exception - Resolving timed out after 5515 milliseconds

by Akash Badole -
Number of replies: 2

Following Error on domainname.com/my

Exception - Resolving timed out after 5515 milliseconds

exceptio error


Average of ratings: -
In reply to Akash Badole

Re: Exception - Resolving timed out after 5515 milliseconds

by Ken Task -
Picture of Particularly helpful Moodlers

Looks like a DNS issue of some sort.  You've not disclosed information concerning many things, so if you can, check the configuration of your DNS on the device/computer and see the DNS servers the device/computer is configured to use.   Then from a terminal or network tool you have on that device, check resolution of well known sites ... like www.google.com.   Then check resolution of your site.

If you were using a Mac or a Linux workstation, cat /etc/resolv.conf  should show the IP addresses of the DNS servers.  8.8.8.8 is google resolver ... might add 2 lines for opendns servers:

nameserver 208.67.222.222 
nameserver 208.67.220.220
Good chance that by the time you read this, the issue might have gone away.

'spirit of sharing', Ken


Average of ratings: -
In reply to Akash Badole

Re: Exception - Resolving timed out after 5515 milliseconds

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

That's an error from 'curl'. A library that's trying to access some external resource. That's odd on the Dashboard page. 

Firstly, switch on Debugging and reproduce the error. We're hoping a trace will show the source of this.

Also, do you have any non-core plugins installed that might be 'calling home' in some way?

Average of ratings: -