ssh failed Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

Question

Note from DigitalOcean Community team: The user @intalix has provided a popular answer to a very similar question on setting up SSH keys here: https://www.digitalocean.com/community/questions/error-permission-denied-publickey-when-i-try-to-ssh?answer=44730 ssh -v root@xx.xx.xx.xxx OpenSSH_6.9p1, LibreSSL 2.1.7 debug1: Reading configuration data /Users/frank_szn/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: /etc/ssh/ssh_config line 56: Applying options for * debug1: Connecting to 45.55.20.113 [45.55.20.113] port 22. debug1: Connection established. debug1: identity file /Users/frank_szn/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /Users/frank_szn/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/frank_szn/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/frank_szn/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/frank_szn/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/frank_szn/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/frank_szn/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/frank_szn/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.9 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c000000 debug1: Authenticating to 45.55.20.113:22 as 'root' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr umac-64@openssh.com none debug1: kex: client->server aes128-ctr umac-64@openssh.com none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<3072<8192) sent debug1: got SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: got SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: ssh-rsa SHA256:xiB0VWociJ19y8/fqsxGcn0OJJeMe8J5TUhii5y05Ms debug1: Host '45.55.20.113' is known and matches the RSA host key. debug1: Found key in /Users/frank_szn/.ssh/known_hosts:3 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/frank_szn/.ssh/id_rsa debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic debug1: Trying private key: /Users/frank_szn/.ssh/id_dsa debug1: Trying private key: /Users/frank_szn/.ssh/id_ecdsa debug1: Trying private key: /Users/frank_szn/.ssh/id_ed25519 debug1: No more authentication methods to try. Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

manzoorsamadin · Answer

Follow these steps: Just check whether your username for the host is correct set 400 permission to your key file

sasidhar · Answer

I was trying to do this on aws.Following is the procedure which worked. clean up the .ssh directory on both master and slave. create same username on both master and slave with (adduser -p ) on the master login as and go home by typing cd (/home/user) ssh-keygen (this will create private and public keys for user) copy the contents of id_rsa.pub from master to /home/user/.ssh/authorized_keys) on slave change permissions of the file authorized_keys to 600 ( chmod 600 authorized_keys) on slave say cd… and check permissions of the directory .ssh on slave. it should be again 600. Now on master login as the and at command prompt say ssh (or ssh user@slaveIDAddress )11 login should be successful. In case you are using jenkins in Jenkins credentials copy the id_rsa (private key) for the . it will connect to slave. Hope I am clear.

sasidhar · Answer

I was trying to do this on aws.Following is the procedure which worked. clean up the .ssh directory on both master and slave. create same username on both master and slave with (adduser -p ) on the master login as and go home by typing cd (/home/user) ssh-keygen (this will create private and public keys for user) copy the contents of id_rsa.pub from master to /home/user/.ssh/authorized_keys) on slave change permissions of the file authorized_keys to 600 ( chmod 600 authorized_keys) on slave say cd… and check permissions of the directory .ssh on slave. it should be again 600. Now on master login as the and at command prompt say ssh (or ssh user@slaveIDAddress )11 login should be successful. In case you are using jenkins in Jenkins credentials copy the id_rsa (private key) for the . it will connect to slave. Hope I am clear.

nosuchip · Answer