You may try edit in /etc/ssh/sshd_config
PasswordAuthentication yes

service sshd restart

I found in messages log information about bad ownership of authorized_keys. So I changed permissions for my /home/USERNAME/.ssh/authorized_keys to 0600 and everything works.

I was trying to do this on aws.
Following is the procedure which worked.

1. clean up the .ssh directory on both master and slave.
2. create same username on both master and slave with (adduser <uname> -p <passwd>)
3. on the master login as <uname> and go home by typing cd (/home/user)
4. ssh-keygen (this will create private and public keys for user)
5. copy the contents of idrsa.pub from master to /home/user/.ssh/authorizedkeys) on slave
6. change permissions of the file authorizedkeys to 600 ( chmod 600 authorizedkeys) on slave
7. say cd.. and check permissions of the directory .ssh on slave. it should be again 600.
8. Now on master login as the <user> and at command prompt say
9. ssh <slave ip address> (or ssh user@slaveIDAddress) 11 login should be successful.
10. In case you are using jenkins in Jenkins credentials copy the id_rsa (private key) for the <user>. it will connect to slave.
11. Hope I am clear.

Hi @ryanpq @nikfarid , I’m having the same issue.

I checked in Digital Ocean Console .ssh/authorized_keys and I have my key there. I did password authentication to Yes, even tried with no. (as someone suggested).

But still no luck, getting the same “Permission Denied (public Key)” issue.

Can you please help me on this.

Thanks,
Dilip Gupta

Hi,
I am trying get SSH access from my Ubuntu 14.04 to Cent OS 7 droplet at digitalocean. But it’s throwing error, “Permission denied (publickey,gssapi-keyex,gssapi-with-mic).”

Again, I am trying to access form filezila SFTP and it’s throwing error:
“Disconnected: No supported authentication methods available (server sent: publickey,gssapi-keyex,gssapi-with-mic)”

I have generated SSH key form my Ubuntu Terminal by command: “ssh-keygen -t rsa” and uploaded / past the public key “id_rsa.pub” to my digitalocean droplet SSH key option.

While I first tried to access SHH connection it asked,
“The authenticity of host ‘1XXXXXXXX’ can’t be established.
ECDSA key fingerprint is XXXXXXXXXXXXXXXXXXXXXXXX.
Are you sure you want to continue connecting (yes/no)?
”
After I type Yes,
it’s through the error, “Permission denied (publickey,gssapi-keyex,gssapi-with-mic)” .

Please advise how to fix it.

Follow these steps:

1. Just check whether your username for the host is correct
2. set 400 permission to your key file

@Dilip7597 I have the same issue
I get Permission denied (publickey,gssapi-keyex,gssapi-with-mic). when trying to ssh through Terminal app.

I just got back from an extended winter holiday, but before the holiday (4-5 weeks ago) I used to ssh connect to my droplet without a problem. I have not changed the ssh keys since then, so it can’t be a problem with that.

I have tried ALL of the above to zero avail

I had luck with the changing the above mentioned permissions on /home/USERNAME/.ssh/authorized_keys in conjunction with changing the permission on the parent ssh folder chmod 700 /home/USERNAME/.ssh

facing the same issue.
Using bash ubuntu for windows and I cannot login to the server.
If i use putty, I get right in

Allow Root User Login in /etc/ssh/sshd_config

# PermitRootLogin no
PermitRootLogin yes

Without further information it is difficult to help you troubleshoot this. According to these logs, the keys on your local computer did not match the public keys on your droplet.

Have you been able to connect to this droplet via ssh before?

Have you used this key on your account with another droplet?

If you continue to have trouble and have not set up a password for your root user you can open a ticket with our support team who can assist you in setting a password to allow you to access the droplet from the console in the control panel in order to investigate or assist you in rebooting your droplet to a recovery environment where you can check that your public key was properly added to your /root/.ssh/authorized_keys file.

Be sure that the public key on /pathToUser/.ssh/idrsa.pub in the droplet is the same file than /pathToUser/.ssh/idrsa.pub in your local machine.

The step
try edit in /etc/ssh/sshd_config
PasswordAuthentication yes

is required on both master and slave

Just adding my two cents. I was trying to ssh by using my ppk and pem file format keys. I was able to login by using my key in the original format id_rsa

ssh -i id_rsa ec2-user@192.168.0.2

I had a similar problem
Resolved with setting the selinux policy

setenforce 0

[root@master11 ~]# getenforce
Disabled
[root@master11 ~]# 

[root@master11 ~]# cat /etc/selinux/config 
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of three values:
#     targeted - Targeted processes are protected,
#     minimum - Modification of targeted policy. Only selected processes are protected. 
#     mls - Multi Level Security protection.
SELINUXTYPE=targeted

had similar problem,
but already setup ssh keys against root when was creating the droplet.

So steps taken:

1. created .ssh directory under new user mkdir /home/<newly added user>/.ssh
2. copied the authorized keys from root cp /root/.ssh/authorized_keys /home/<newly added user>/.ssh

Had this problem for AWS CLI on my Mac Terminal

1. Create access key from AWS Console
2. Installed AWS CLI v2
3. Created and run new EC2 instance using newly created existing access key
4. open terminal from mac entered ls to see if my .pem file which is the access key is found otherwise change directory for example cd documents
5. then enter chmod 0400 filename.pem 6 then try to ssh in again example ssh ec2-user@xx.xxx.xx.xxx -i filename.pem