Skip to main content

Unable to SSH - Error: Permission denied (publickey,gssapi-keyex,gssapi-with-mic)

Comments

4 comments

  • cPanelLauren
    The issue is here: debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic debug1: Trying private key: /Users/xxxx.xxxx/.ssh/id_dsa debug3: no such identity: /Users/xxxx.xxxx/.ssh/id_dsa: No such file or directory debug1: Trying private key: /Users/xxxx.xxxx/.ssh/id_ecdsa debug3: no such identity: /Users/xxxx.xxxx/.ssh/id_ecdsa: No such file or directory debug1: Trying private key: /Users/xxxx.xxxx/.ssh/id_ed25519 debug3: no such identity: /Users/xxxx.xxxx/.ssh/id_ed25519: No such file or directory debug1: Trying private key: /Users/xxxx.xxxx/.ssh/id_xmss debug3: no such identity: /Users/xxxx.xxxx/.ssh/id_xmss: No such file or directory
    The private key matching the public one you provided is unable to be found. Does /Users/xxxx.xxxx/.ssh/id_xmss or any of the other noted files exist? And if so what are their permissions?
    0
  • Cityhues
    Hi cPanelLauren - thanks for the response. Actually - none of those Private keys exist in my local .ssh folder. I expected the system to be asking for the private key at /Users/xxxx.xxxx/.ssh/id_rsa (which does exist with permissions 600 for user xxxx.xxxx) . I had created a new id_rsa keyset and installed the private key locally ... but when I ssh, the system is not looking for that private key.
    0
  • ItsMattSon
    Hi @Cityhues - Just thinking out loud here. Have you added the Public key to your authorized_keys file in ~/.ssh ? The permissions of ~/.ssh on the server should be 0700 and the file ~/.ssh/authorized_keys on the server should be 0600. Best you also double-check the owner and group are set to your user also, xxxx.xxxx
    0
  • Cityhues
    Hi @Cityhues - Just thinking out loud here. Have you added the Public key to your authorized_keys file in ~/.ssh ? The permissions of ~/.ssh on the server should be 0700 and the file ~/.ssh/authorized_keys on the server should be 0600. Best you also double-check the owner and group are set to your user also, xxxx.xxxx

    Thanks @ItsMattSon for your reply. I reset the pub/priv key pairs and rechecked all the permissions. That seemed to be the solution.
    0

Please sign in to leave a comment.