Related

Tool [NEW] Bandwidth Pricing Calculator Tool
Can I force a new IP instead of reusing the last one? Question Question
Are there plans to implement availability in the central US? Question Question

Question

Why can't login my VPS with SSH-console

Posted March 27, 2016 5.2k views
DigitalOceanNetworking

My new VPS was set up with Singapore server farm yesterday.
Today, my ssh connection got disconnected twice unintentionally in 3 hours. The worst of all, it got disconnected for 1 hour or so just now, showing

** connection time out (port:22)**

and I felt annoyed so that I destroy my server image(I thought it is my setup was causing problem) and try to rebuild the whole server

Nonetheless, when I started over with a new server image, and tried connecting it with (new ipaddress and also my ssh-public key), it still shows “connection time out”.

Although the whole time, I keep one of my console “ping xxx.xxx.xxx.xxx” to give me a clue about the networking status. It looks obvious that the ping response time is quite poor to your server, sometimes it interrupts. However, I could always browser your digitalocean User dashboard all the time.

Add a comment
jeffery2016
By:
jeffery2016

Related

Tool [NEW] Bandwidth Pricing Calculator Tool
Can I force a new IP instead of reusing the last one? Question Question
Are there plans to implement availability in the central US? 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
jeffery2016 March 27, 2016

Now it drops me again:
64 bytes from 128.199.123.97: icmpseq=1351 ttl=46 time=204 ms
64 bytes from 128.199.123.97: icmpseq=1352 ttl=46 time=1096 ms
64 bytes from 128.199.123.97: icmpseq=1353 ttl=46 time=143 ms
64 bytes from 128.199.123.97: icmpseq=1354 ttl=46 time=142 ms
64 bytes from 128.199.123.97: icmp_seq=1355 ttl=46 time=143 ms

(nothing had echoed 3 minutes earlier till now)

Reply Report
Woet March 27, 2016

Works fine here, must be your internet connection / firewall. 

MacBook-Air:~ Woet$ ssh 128.199.123.97
root@128.199.123.97's password:
Permission denied, please try again.
root@128.199.123.97's password:
Reply Report
sudhama July 4, 2016

We have experienced this as well. .There seems to be something unstable in the setup somewhere.

We had a droplet with a user and the public and private key set up fine and PermitRootLogin set to no. We created another droplet from this one, reset the password, and weren’t able to login with that user. We created another user and public key but we weren’t able to login with the new users permissions. Somehow it allowed the old one. Once I switched off my mac, and switched it on again, can’t login to the server! Can’t login from the web console of DO. Anyone solved for this?

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help