Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Automatic power cycling when down? Question Question
Followed instructions. Setup SSH keys but server still prompts for password Question Question

Question

My network connection has gone down and I cannot ssh into server or access server through web console

Posted January 8, 2017 2.2k views
Configuration ManagementUbuntu 16.04

I am unsure if this is related, but after upgrading to Mac SierraOS I have had to recreate my ssh key and update that in Digital Ocean. After doing so, I haven’t been able to access my console via the DO web console or through ssh connection.

I tried resetting the root password to get access to my server and no luck there either.

code
ssh: connect to host 123.456.78.111 port 22: Operation timed out
Add a comment
By:
leannatnorwood

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Automatic power cycling when down? Question Question
Followed instructions. Setup SSH keys but server still prompts for password 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.

×
Submit an Answer
2 answers
leannatnorwood January 8, 2017

I am not super familiar with server side stuff and have been learning as I go. The site has been up and running for months, so I’m not sure what happened here when I updated my SSH key

Reply Report
jtittle1 January 8, 2017

@leannatnorwood

If you’re currently using an SSH Key on you Droplet, resetting the root password will not work as root access using a password is disabled when an SSH Key is provided during deployment.

That said, if you provided one SSH Key before you updated to macOS Sierra, then created a new one and replaced the old key with the new one, the old one is still on your server as that’s what it was deployed with. The new one will only deploy to new droplet instances.

The best thing to do in this case would be to submit a support ticket through the DO CP and see if they can get in to your Droplet and help you to either recover the key that is on the server or set the new key in its place.

Without the SSH Key that exists on the server and the private key locally to gain access, you won’t be able to get in.

Backing up your SSH keys is super important, for cases such as this especially!

Reply Report

Related

Looking for something else?

Ask a new question Search for more help