Question

ssh: connect to host 128.xxx.xxx.xx port 22: Connection refused?

Hi everyone, I know this is rather a typical problem, I’m new with DO, been trying couple of times already by now, and even found similar issues already in the forum, but still couldn’t solve the problem yet.

Just created an Ubuntu droplet, which is now in its active state, tried many times logging in with SSH, but couldn’t get through, followed the instruction found here, but still can’t manage to get through, got the following error in return instead :

ssh: connect to host 128.xxx.xxx.xx port 22: Connection refused

Try restarting the instance, but still nothing happened, anyone with a clue on this? Really appreciate all the help I can get. Thanks everyone.

Cheers,

Subscribe
Share

@ryanpq okay than. Thanks for the help. Have a nice weekend.

Cheers,

That would indicate that the issue is not just with your ssh service and your droplet itself is unresponsive. I would recommend rebooting the droplet and if you are still unable to connect, open a ticket with our support team so they can investigate.

@ryanpq

If you were able to verify that the service did start back up via the console in the control panel

  • Now that’s the thing, I couldn’t verify that, would that imply my port 22 is being blocked by my system administrator?

Checking VNC Connection…

than

Failed to establish a connection to the console. Please reload.

It kept giving me that same message all over.

What do you think?

Cheers,

If you were able to verify that the service did start back up via the console in the control panel I would check if port 22 is blocked on your local network.


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.

This question was answered by @ryanpq:

That would indicate that the issue is not just with your ssh service and your droplet itself is unresponsive. I would recommend rebooting the droplet and if you are still unable to connect, open a ticket with our support team so they can investigate.

You can see the comment here.