I want to SSH into my Raspberry Pi, but for security reasons also don't want to keep the standard password raspberry
for the standard user pi
. There fore I used passwd
to change pi
's password. However, when I then try to ssh I get the errors
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,password)
These errors are also the subject of a number of other threads, but none have answers that solve the problem for me.
I think it has something to do with the public key and it not changing with the password when one uses passwd
. The reason being that if I change the password back to raspberry
I can SSH just fine.
-EDIT- Verbose ssh added
-bash-4.1$ ssh -v pi@xxx.xxx.xxx.xxx
OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx] port 22.
debug1: Connection established.
debug1: identity file /home/nfs/shijgenaar/.ssh/identity type -1
debug1: identity file /home/nfs/shijgenaar/.ssh/identity-cert type -1
debug1: identity file /home/nfs/shijgenaar/.ssh/id_rsa type -1
debug1: identity file /home/nfs/shijgenaar/.ssh/id_rsa-cert type -1
debug1: identity file /home/nfs/shijgenaar/.ssh/id_dsa type -1
debug1: identity file /home/nfs/shijgenaar/.ssh/id_dsa-cert type -1
debug1: identity file /home/nfs/shijgenaar/.ssh/id_ecdsa type -1
debug1: identity file /home/nfs/shijgenaar/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.7p1 Raspbian-5+deb8u3
debug1: match: OpenSSH_6.7p1 Raspbian-5+deb8u3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-sha1 none
debug1: kex: client->server aes128-ctr hmac-sha1 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<2048<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: Host 'xxx.xxx.xxx.xxx' is known and matches the RSA host key.
debug1: Found key in /home/nfs/shijgenaar/.ssh/known_hosts:4
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
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: Trying private key: /home/nfs/shijgenaar/.ssh/identity
debug1: Trying private key: /home/nfs/shijgenaar/.ssh/id_rsa
debug1: Trying private key: /home/nfs/shijgenaar/.ssh/id_dsa
debug1: Trying private key: /home/nfs/shijgenaar/.ssh/id_ecdsa
debug1: Next authentication method: password
pi@xxx.xxx.xxx.xxx's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
pi@xxx.xxx.xxx.xxx's password:
ssh -v <your_raspberrypi>
? That would provide you a much more verbose error message. – Dmitry Grigoryev Mar 28 '17 at 15:48ssh -vv
to get more details and on the pi side, have a look in/var/log/auth.log
. – goldilocks♦ Mar 28 '17 at 15:58abc123
, and double check thepi
user can log in locally with that. The stuff about the public/private keys is just there because you have some on the remote computer and ifsshd
says it will accept them, thessh
client will try and apply them automatically. When that fails it falls back to password. You will see much the same thing if you do this when the password is working. – goldilocks♦ Mar 29 '17 at 12:08