Question
Was previously able to SSH into droplet but suddently it's not working?? Resetting keys unsuccessful..
Not sure what exactly this is telling me? The file [~/Users/austinmiles/.ssh/id_rsa] exists, why wouldn’t it be found? Also, why is it searching for a dsa key?
OpenSSH_6.9p1, LibreSSL 2.1.8 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 21: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 192.241.135.48 [192.241.135.48] port 22. debug1: Connection established. debug1: identity file /Users/austinmiles/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /Users/austinmiles/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/austinmiles/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/austinmiles/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/austinmiles/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/austinmiles/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/austinmiles/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/austinmiles/.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_7.2p2 debug1: match: OpenSSH_7.2p2 pat OpenSSH* compat 0x04000000 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to 192.241.135.48:22 as ‘root’ debug3: hostkeys_foreach: reading file “/Users/austinmiles/.ssh/known_hosts” debug3: record_hostkey: found key type ED25519 in file /Users/austinmiles/.ssh/known_hosts:6 debug3: load_hostkeys: loaded 1 keys from 192.241.135.48 debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-ed25519-cert-v01@openssh.com,ssh-ed25519 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-ed25519-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-rsa,ssh-dss debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256 debug2: kex_parse_kexinit: ssh-ed25519,ssh-rsa,rsa-sha2-512,rsa-sha2-256 debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr debug2: kex_parse_kexinit: hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-ripemd160-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160 debug2: kex_parse_kexinit: hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-ripemd160-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160 debug2: kex_parse_kexinit: none,zlib@openssh.com debug2: kex_parse_kexinit: none,zlib@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug1: kex: server->client chacha20-poly1305@openssh.com <implicit> none debug1: kex: client->server chacha20-poly1305@openssh.com <implicit> none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ssh-ed25519 SHA256:n06JJ3Chv7S9s9czi5hssBIz7YC9/LHz7RcknyynRSg debug3: hostkeys_foreach: reading file “/Users/austinmiles/.ssh/known_hosts” debug3: record_hostkey: found key type ED25519 in file /Users/austinmiles/.ssh/known_hosts:6 debug3: load_hostkeys: loaded 1 keys from 192.241.135.48 debug1: Host ‘192.241.135.48’ is known and matches the ED25519 host key. debug1: Found key in /Users/austinmiles/.ssh/known_hosts:6 debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /Users/austinmiles/.ssh/id_rsa (0x7fb729e13e20), debug2: key: /Users/austinmiles/.ssh/id_dsa (0x0), debug2: key: /Users/austinmiles/.ssh/id_ecdsa (0x0), debug2: key: /Users/austinmiles/.ssh/id_ed25519 (0x0), debug1: Authentications that can continue: publickey debug3: start over, passed a different list publickey debug3: preferred publickey,keyboard-interactive,password debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/austinmiles/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg ssh-rsa blen 279 debug2: input_userauth_pk_ok: fp SHA256:PjB2UOY8KWCs7k2tzyWNVvQDTv2Uuy3HclfAB8YlIUM debug3: sign_and_send_pubkey: RSA SHA256:PjB2UOY8KWCs7k2tzyWNVvQDTv2Uuy3HclfAB8YlIUM debug1: Authentications that can continue: publickey debug1: Trying private key: /Users/austinmiles/.ssh/id_dsa debug3: no such identity: /Users/austinmiles/.ssh/id_dsa: No such file or directory debug1: Trying private key: /Users/austinmiles/.ssh/id_ecdsa debug3: no such identity: /Users/austinmiles/.ssh/id_ecdsa: No such file or directory debug1: Trying private key: /Users/austinmiles/.ssh/id_ed25519 debug3: no such identity: /Users/austinmiles/.ssh/id_ed25519: No such file or directory debug2: we did not send a packet, disable method debug1: No more authentication methods to try. Permission denied (publickey).
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.
Thanks for this @jtittle, how would I be able to confirm that I’m locked out? I did deploy with SSH unfortunately. Is there a specific lockout period? Do I have any other options. Do the keys need to match the ones used via a github deploy? I don’t quite understand the process of agent-forwarding.
@abm
The
Permission Deniederror is a result of one of two things.1). Your local private key (on your Mac) doesn’t match the public key on your Droplet;
2). Incorrect permissions on one or both keys.
…
If your local private key doesn’t match the public key on the Droplet, authentication will fail. Likewise, if you generate a new key pair locally and fail to update the public key on the Droplet, authentication will fail.
The private key you attempt to authenticate must match the public key on the server you’re trying to connect to using:
If permissions are incorrect on the
authorized_keysfile or the.sshdirectory on either end, login will also fail.…
Generally when you’re locked out from SSH after repeated failed logins, the block is temporary, unless you have a firewall (such as
ufw) active, in which case, you may need to login to console from the DigitalOcean control panel and login withrootand therootusers password.If you deployed with SSH Keys, the
rootuser won’t be setup with a password, and you may be locked out of the server as console doesn’t accept SSH Keys – only therootpassword.