Connection issues?

Posted July 8, 2013 17.5k views
How come at times I cannot connect to my server? I have a LEMP stack configured and often times throughout the day, I'll try to connect to the site only for it not to connect. During these times I cannot access the server through putty, or FTP. The "downtimes" could last upwards of 2+ minutes some times. Is something configured improperly or is this another issue?
1 comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
27 answers

Same here. Experiencing it now and this is the really first time that I’m having a real issue on DO. What’s weird is that I have several VPS all in the same location (Singapore) but only my Rails VPS (created from 1-click app) is down. When I’m trying to ping it, it shows:

PING 188.166.X.X (188.166.X.X): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10

We are planning to use DO for some of our production apps and this issue is scaring the s**t out of me. Has anyone find a way to fix it and keep it that way?

Please provide a traceroute or mtr to your droplet in a support ticket if you experience this again, it will help us identify the cause of your droplet's downtime better. Thanks!
... I cannot access the server through putty, or FTP."

What kind of error message(s) do you get?
The error message I get from putty is "connection timed out". When trying to connect to the website hosted on the droplet I get "Google chrome could not connect to".

It's in the NY region. Next time I see it happening, I'll do a traceroute and make a ticket.
I am experiencing this problem as well and it seems to be due to some kind of standby feature in either KVM or the network equipment (the droplet is located in ams1). I eventually worked around the problem by running "ping -c 1" every 5 minutes. I first tried simply making some disk IO happen every 5 minutes but this did not solve the problem.
If you want to reproduce the problem, try to do the following:

1. Create a 512 or 1 GB droplet (any droplet will probably do)
2. Select Ubuntu 12.04 x32 (guess it will happen with other images as well though I haven't tested that)
3. Ping the droplet 1-3 times once it is ready (you should get a response immediately)
4. Wait 20 minutes before pinging it again (you should now get timeout / no response)
Dan, I was not able to reproduce this. I've created a 512MB droplet in NY with Ubuntu 12.04 x32 as the base image. I was able to ping it after 20 minutes.
Kamal, I will try to trigger the problem using my current droplet. I'll post a screenshot in about an hour.
Strange. I can't seem to reproduce it with a 20 minutes delay. I'll try to let it idle for 2 hours to see if it's simply a matter of waiting long enough. I'll get back to you later.
I am no longer able to reproduce the problem. I could do it multiple times a few days ago but either you guys fixed the issue or it was simply a network problem somewhere (which lasted for more than a day). I have now removed the ping command from crontab and then I'll see if it happens again the next time I need to access the server.
Previous 1 2 3 Next