On a regular basis lately I am unable to access any of the sites on my VPS server. The problem lasts for 30-60 minutes then seems to go away. I know it is not the server's fault because other people in other geographic locations can access it fine (tested with http://www.isup.me/ and others). I know it is not my local ISP because the same things happen when I am at work on the other side of town. I have run several traceroutes and the path to the server seems to die before it completes: d:\Users\Chad>tracert musicedmagic.com Tracing route to musicedmagic.com over a maximum of 30 hops: 1 1 ms 1 ms 1 ms unknown [192.168.1.1] ......... 17 81 ms 75 ms 75 ms dc03r01bg01.scalabledns.com [199.48.68.38] 18 78 ms 75 ms 75 ms dc03r09sw01.scalabledns.com [199.48.68.82] 19 75 ms 75 ms 76 ms 98-232-229-199.rdns.scalabledns.com [199.229.232 .98] 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Code (markup): If this was a once in a while problem I wouldn't bother with it, but it seems like it is growing more and more frequent, almost always when I am about to save something I have been working on for hours... Any idea how I can work around this issue or fix it completely?
check your dns ( in internet connection) use 4.4.8.8 and 8.8.8.8 as dns servers , the problem appears to be he dns servers which are not sending requests, usually happens with low quality dns providers like small town isp's
I'll second that. Those two servers are google DNS, something I basically HAVE to use to get to half the sites I want to access given how badly time-warner DNS inhales the proverbial equine of short stature. Changing your DNS to manual and using those two address should fix things. -- EDIT -- CORRECTION, 4.4.8.8 is incorrect! Google DNS is IPV4: 8.8.4.4 8.8.8.8 IPV6: 2001:4860:4860::8888 2001:4860:4860::8844 https://developers.google.com/speed/public-dns/ Thought that didn't look right!
I've tried doing this (changing the DNS servers to the Google ones) but even after the change and a reboot this problem is still occasionally popping up. I changed the DNS on my local machine and also on my router but I am still intermittently unable to access my server even though isup.me reports that the sites are up and functioning. Anything else I could possibly do to fix this or work around the bad connection?
Looking at your tracert, and running one here to compare, the failure is at the final server, so the problem IS INDEED on the hosting end. What is that... scalabledns.com??? Ah, Enzu cloud hosting (so NOT a VPS) -- that could be the problem right there as it may be sending you and/or your region to a different server than elsewhere. Part of why I don't trust "cloud hosting" or any of that nonsense -- If that is indeed what/who you are hosted with, my advice would be to get a REAL DNS host, a REAL server or real VPS... I really don't trust "cloud hosting" since it seems to always have issues just like the one's you're encountering -- it's just too damned complex for it's own good under the hood -- no matter how "simple" the front-end might be.
I haven't had any problems with the VPS service itself, but are you saying the connectivity problem is on their end somehow? Does it mean anything if a service like isup.me reports that my site is up when I can't get to it? Is there anything I can say to them that would make them think I know what I am talking about if I contact them?