Related

Is it possible to take a snapshot of a volume, destroy the volume, then restore it from the snapshot? Question Question
my SGP1 server can't access Question Question

Question

Error Connection Timed out while using putty (SSH)

Posted January 19, 2020 29.6k views
DigitalOcean Accounts

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?

Add a comment
harshsmith
By:
harshsmith

Related

Is it possible to take a snapshot of a volume, destroy the volume, then restore it from the snapshot? Question Question
my SGP1 server can't access Question Question

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.

×
3 answers
KFSys January 19, 2020

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

Reply Report
  • KFSys January 19, 2020

    I just noticed something else as well. When I try to ping your droplet as you’ve mentioned :

    ping 131.103.20.167
PING 131.103.20.167 (131.103.20.167) 56(84) bytes of data.
--- 131.103.20.167 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1001ms

    It seems to be offline. Have you turned it off or it should be running? If it should be running then I’ll recommend following my second advice from the previous reply.

    Regards,
    KDSys

    Reply Report
harshsmith January 19, 2020

@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?

Reply Report
  • KFSys January 20, 2020

    Hi @harshsmith,

    Can you use the console for your droplet from your control panel and connect the server? From there you should be able to try out a few things like 

    service sshd restart

    and 

    service network restart

    Once they restart, please try again to ping,ssh to your droplet.

    Regards,
    KDSys

    Reply Report
shomikx December 28, 2020
Show answer This answer has been marked as resolved by shomikx.
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help