Question

Error Connection Timed out while using putty (SSH)

I can’t connect to my droplet through SSH. This was working fine until I click on reset root password and the server rebooted. The new password got sent to me but now I can’t connect from ssh or pull my GitHub repository.

Also, just running a simple ping 131.103.20.167 on the console fails with “Network Unreachable” error message.

And my website also stopped working. The server is turned on, my IP address is correct. So what’s going on?

Subscribe
Share

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.

In my case the Firewall which I enabled during LetsEncrypt SSL installation. Simply did the following and my SSH started working.

sudo ufw allow ssh

@KDSys This is my IP: 157.230.244.188

I just used that to run some test on the console and this is what i got:

$ ping 131.103.20.167

Connect: Network is unreachable

Same error if i use my own IP 157.230.244.188 doesn’t connect on the console but the result is different when I try to ping locally on git bash

$ ping 157.230.244.188

Pinging 157.230.244.188 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 157.230.244.188:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

My network is fine, I can connect to other services locally and ssh into servers running on port 22 TCP but nothing works on the console.

Visiting my website online using my domain or IP address still shows a connection timed out error.

How do i open a ticket?

Hi @harshsmith,

There are a couple possible reasons for this:

1.) You are on a network which blocks traffic to port 22. Trying your connection from another network or device would be the best way to quickly test for this.

2.) The ssh service on your droplet is not running.

I would advise trying to access your droplet via the console in the control panel if you use password based authentication or have set a root password. This should allow you to check on and restart the ssh service if needed. If you do not have a root password I would recommend trying a reboot from the control panel to see if the ssh service comes back up.

Regards, KDSys