Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
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.
Accepted Answer
The issue is within your sshd_config file.
Here is the ULTIMATE solution to this issue:
Log as root to your Ubuntu server
Use vim or nano to edit the contents of /etc/ssh/sshd_config
Eg. vi /etc/ssh/sshd_config or nano /etc/ssh/sshd_config
Now go to the very bottom of the file (to the line with PasswordAuthentication) - Change the value next to PasswordAuthentication from no to yes.
It should now look like this:
# Change to no to disable tunnelled clear text passwords
PasswordAuthentication yes
sudo service sshd reloadWith this done, you can now set up your new SSH key for your LOCAL device. To do this, you can run the following from your LOCAL device, not the server:
ssh-copy-id username@droplet.ip
(Make sure to replace username with your username on the droplet and droplet.ip with the full IP address of your droplet)
With this done, you should be good to go, connecting with SSH keys!
Hi, just solve this issue with the same method above.
There seems to be some problem with the setup of Droplet.
The .ssh/authorized_keys wasn’t correct originally.
The “vim -d id_rsa.pub .ssh/authorized_keys” said they are different.
then do the third command.
and everything works.
hope this helps.