Permission denied (publickey)

Hello there,

You can check our article on How to Upload an SSH Public Key to an Existing Droplet

https://www.digitalocean.com/docs/droplets/how-to/add-ssh-keys/to-existing-droplet/

You can access the droplet from the DigitalOcean console and then temporary enable the PasswordAuthentication on your droplet and access the droplet with a password to upload the ssh-key.

If you haven’t created new pair of keys you’ll need to do that first.

You can enable PasswordAuthentication for your Droplet by modifying your /etc/ssh/sshd_config file. Once set to Yes restart the SSH service and connect via an SSH client for a more stable connection. You can then modify your ~/.ssh/authorized_keys file to add the appropriate public key.

This change can be made from the DigitalOcean’s console. If you’re having issues accessing the console you can then reach to our amazing support team that can help you further with this.

To enable the PasswordAuthentication follow these steps:

2. Login to the console on the DigitalOcean website.
3. Type sudo nano /etc/ssh/sshd_config
4. Change PasswordAuthentication from “no” to “yes” and save the file
5. Open a terminal on your computer and type ssh username@[hostname or IP address] or if on a Windows box use PuTTY for password login making sure authentication parameters aren’t pointing to a private key
6. Login with a password
7. Type sudo nano ~/.ssh/authorized_keys
8. Paste public key text here and save the file
9. Type sudo nano /etc/ssh/sshd_config
10. Change PasswordAuthentication from “yes” to “no” and save the file
11. Log out and attempt to log back in (if using PuTTY make sure you set up auth parameters to point to your private key)

You can then upload the key using this command:

ssh-copy-id -i ~/.ssh/mykey user@droplet

Hope that this helps! Regards, Alex

For those who face the same problem. It turns out, when I reset my through chsh, I accidentally set root sh to be bash instead of /bin/bash.

To fix this:

• Got to Recovery tab in Digital Ocean.
• Choose Boot From Recovery ISO
• Restart the droplet and connect to it through ssh
• Now you are booted from recovery OS, you need to mount your harddrive, run tmux and choose 1 to Mount your hard drives.
• Go to interactive mode
• Change the content of /mnt/etc/passwd, change line starting with “root” to this:

root:x:0:0:root:/root:/bin/bash

• Logout, switch back to Boot from Hard Drive
• Restart the droplet and try to connect, if credentials are okey, you will successfully login.

@snapshooter Now I created a new droplet (NOT from snapshot), and I can connect regularly with the same keys.

So there is not an issue with SSH keys. I don’t know how to troubleshoot that droplet now. I believe it’s because it does not have a default bash anymore.