Adding public key to an existing droplet failed

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

Hello,

When you log in with SSH, do you identify the key with ssh -i /path/to/private/key ? This will ensure you are using the right SSH key when logging in. Sometimes, if you have alot of key pairs; the system will fail due to too many keys being passed. Make sure with the above command you change /path/to/private/key to the actual path of your private key. I imagine it’s likely .ssh/idjenkinsrsa based on your public key path.

Specifying the private key you want to use, that matches the public key you added, will fix this.

As for if you can remove the keys and add them, sure! Just remove the 2 keys from the ~/.ssh/authorized_keys file on the droplet and then re-add your key. You can even add it manually if you want, but just copying it and pasting it into the file.