Question

I cannot connect (ping or ssh) to my droplet

  • Posted August 21, 2014

I was able ssh into my droplet a while ago, and I also deployed a Rails web app. It was working as I was able to access the webpage from the IP. However, I haven’t been able to ssh to the droplet for a 5 or 6 hours now.

When I go to the ‘console’ page for the droplet, it says “Failed to establish a connection to the console. Please reload.” I also tried power off and restart the server, but it didn’t work.

Please advise and thanks.

Subscribe
Share

Hi!

Try to go to Droplet control panel “Settings->Networking”. What do you see there?

Regards

I just created droplet ubuntu. I can not connect to it by ssh. I created public key and added key already to my droplet. I dont have floating IP in networking tab. What should I do to access to my droplet?

Hi, I have go to http://www.infobyip.com/sshservertest.php and test my droplet. But it say: Cannot connect to 162.243.211.232:22 Please help me connect to my droplet. Thanks!


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

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.

Check your firewall rules , try sudo ufw allow OpenSSH

FAIL Cannot connect to 159.203.105.139:22

SSH server tester (SSH connection checker) is an ssh client that tests ssh server connectivity and accessibility from the Internet by establishing connection to the specified ssh server. Testing the ssh connectivity does not require ssh credentials since SSH tester does not need to log into ssh account. It connects to the server and obtains ssh server fingerprint which confirms that server is online and responding to requests via ssh protocol. SSH server test will be performed from our IP address (IPv4: 45.79.3.202, IPv6: 2600:3c00::f03c:91ff:fe67:aa7c). You should be able to see it in the ssh server logs if connection is successful.

It works now without me doing anything, but it was really frustrating for this to happen.