ping request timeout, I can't connect to my droplet using ssh or even telnet

I recently lost connection to my server, after making some configuration( which could possibly or not) be the cause when I ping my IP the request get timeout, am not able to connect either using ssh or telnet.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Site Moderator
Site Moderator badge
January 17, 2024

Heya @epaynet,

It seems like the Droplet’s network is not working OR the Droplet itself is down.

First, use the recovery console to enter your Droplet (if it’s online) and bring your network back up, possibly, you can reverse the configurations you did.

The Recovery Console provides out-of-band access and is available regardless of your network settings. It emulates the access you would have if you were sitting down with a keyboard and monitor attached to the actual server. You can use this feature to log in and revert bad settings to regain normal access.

If the Droplet is offline, then try to start it and again use the recovery console to try and enter it. If that doesn’t work, then you’ll need to contact DigitalOcean’s Support for further assistancem who will be more than happy to assist you with your account issue! :)

Hope that helps! - KFSys.

Bobby Iliev
Site Moderator
Site Moderator badge
January 17, 2024

Hey there!

Sorry to hear about the troubles you’re facing with your Droplet. Let’s see if we can sort this out together. 😊

First off, it’s great that you’re keeping an eye on the changes you’ve made – that’s always key in troubleshooting. Now, onto the steps:

  1. Check Droplet Status: Pop into your DigitalOcean control panel. Make sure your Droplet is up and running. Sometimes, it’s the simplest thing we overlook. If the Droplet is not running, try to reboot it.

  2. Firewall Settings: Since you mentioned a recent configuration change, let’s start there. Double-check your firewall settings (both on DigitalOcean and within your Droplet). A firewall rule might be blocking your SSH or ICMP traffic.

  3. Console Access: Use the DigitalOcean console access feature. This can be a lifesaver when SSH is playing hard to get. It’s like having a direct line to your server without the need for SSH.

  4. Logs: Check out the logs (/var/log/auth.log is a good start for SSH issues). They might hold clues about what’s going wrong.

  5. Revert Recent Changes: If you suspect a recent change is the culprit, try rolling it back. If you’ve made changes to the SSH configuration, for instance, and have a backup of the original file, try restoring it.

  6. Reach Out to Support: If all else fails, don’t hesitate to contact DigitalOcean’s support team. They’re pretty awesome and can often provide insights we might miss.

Let me know how it goes!



Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel