How to change SSH Authorized Keys

Hello, @diogohenriques

The Copy/Paste functionality of our web console is a bit odd; the code backing it is custom due to the way the VNC window is implemented for accessing your Droplet. It isn’t a good idea, in my experience, to rely on the console for long copy/pasting like an SSH key.

My recommended method to get the key on the Droplet is over SSH itself. 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 should do the job for you as well.

The other option is to temporary enable the PasswordAuthentication from no to yes in order to access your droplet using password and then once you’ve entered your key to disable the PasswordAuthentication again. This way is considered more secure than uploading the key to a Dropbox in case you don’t have any other server to us.

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)

Another thing is to check this article when you’ve regained access to the droplet:

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

Hope that this helps! Regards, Alex