Question

I'm trying to install droplet but am stuck at SSH password

First droplet was 32-bit but install failed because there is no 32-bit Docker. Destroyed droplet and rebuilt as 64-bit. As expected, I needed to run ssh-keygen -R IP because the SSH key changed but IP didn’t.

No luck, it still demands a password! I’ve tried removing keys, regenerating keys and am stuck by my own security system. I’m not much of a hacker I guess!

Subscribe
Share

It looks like it’s offering your key but the server is not accepting it, or the key contained in /Users/Halcyon/.ssh/id_rsa is not the correct one.

Here is my verbose ssh XXed out IP and host key

OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 debug1: Reading configuration data /etc/ssh_config debug1: /etc/ssh_config line 20: Applying options for * debug1: /etc/ssh_config line 53: Applying options for * debug1: Connecting to IPX>XXX>XX [IP>XXX>XX>X] port 22. debug1: Connection established. debug1: identity file /Users/Halcyon/.ssh/id_rsa type 1 debug1: identity file /Users/Halcyon/.ssh/id_rsa-cert type -1 debug1: identity file /Users/Halcyon/.ssh/id_dsa type -1 debug1: identity file /Users/Halcyon/.ssh/id_dsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH* debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA XXXXXXXXXX debug1: Host ‘PX>XXX>XX’ is known and matches the RSA host key. debug1: Found key in /Users/Halcyon/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct 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,password debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/Halcyon/.ssh/id_rsa debug1: Authentications that can continue: publickey,password debug1: Trying private key: /Users/Halcyon/.ssh/id_dsa debug1: Next authentication method: password


Submit an 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.

If you selected a key when creating the droplet and you’re still being asked for a password when logging into it, that means your SSH client is not providing the key (or not providing the correct key) when you connect. You can diagnose this by increasing the verbosity of your SSH client by adding the ‘-v’ argument (and you can it more than once to get more output)

or, even just:

chown -R $USER:$USER ~/.ssh

A couple of things to try:

first, remove servers from known_hosts do this:

ssh-keyscan yourdomainn.or.ip.address 

secondly, make sure permissions on your .ssh folders and home folder are good:


chmod go-wrx ~
chmod 700 ~/.ssh
chmod 600 ~/.ssh/authorized_keys

This comment has been deleted

Use the console to run this.