jgold
Posts: 5
Joined: Fri Aug 29, 2014 1:22 am

SSH Permission denied

Sun Jan 25, 2015 12:48 am

Hi,

I've got a new Raspberry Pi B+ set up with the latest firmware running Raspbian from Noobs_v1_3_11. I'm trying to create a ssh connection to it using the built in "pi" user and "raspberry" password and I keep getting "permission denied".

I've been going through the "Raspberry Pi Cookbook" and searching the web but I can't seem to find the missing piece that would allow SSH logins. Everything I've found says that the Pi user is already set up for SSH and that all I need to do is enable it with raspi-config. (Which was already enabled but I disable and re-enabled it again anyway).

I've tried logging in from different computers with the same result. I used the -v command from my mediaserver and below is the result. I'm surprised this isn't working since I did a clean install on Thursday and haven't really done anything that might bork it up.

Does anyone have any idea what I'm missing?

Thanks.


[email protected]:~/.ssh$ ssh 192.168.1.170 -l pi -v
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 192.168.1.170 [192.168.1.170] port 22.
debug1: Connection established.
debug1: identity file /home/jgold/.ssh/id_rsa type -1
debug1: identity file /home/jgold/.ssh/id_rsa-cert type -1
debug1: identity file /home/jgold/.ssh/id_dsa type -1
debug1: identity file /home/jgold/.ssh/id_dsa-cert type -1
debug1: identity file /home/jgold/.ssh/id_ecdsa type -1
debug1: identity file /home/jgold/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/jgold/.ssh/id_ed25519 type -1
debug1: identity file /home/jgold/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.2_hpn13v11 FreeBSD-20130515
debug1: match: OpenSSH_6.2_hpn13v11 FreeBSD-20130515 pat OpenSSH* compat 0x04000000
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr [email protected] none
debug1: kex: client->server aes128-ctr [email protected] none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA 0e:63:03:b6:dd:59:35:3b:ab:4d:0a:54:52:90:e0:66
debug1: Host '192.168.1.170' is known and matches the ECDSA host key.
debug1: Found key in /home/jgold/.ssh/known_hosts:2
debug1: ssh_ecdsa_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: Trying private key: /home/jgold/.ssh/id_rsa
debug1: Trying private key: /home/jgold/.ssh/id_dsa
debug1: Trying private key: /home/jgold/.ssh/id_ecdsa
debug1: Trying private key: /home/jgold/.ssh/id_ed25519
debug1: Next authentication method: password
[email protected]'s password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
[email protected]'s password:[I tried "raspberry" again, very carefully]
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.

jgold
Posts: 5
Joined: Fri Aug 29, 2014 1:22 am

Re: SSH Permission denied

Sun Jan 25, 2015 2:07 am

Never mind. I discovered that even through my IP address on the Raspberry was 192.168.1.170, that address was already taken by a FreeBSD box on the network. I was trying to log on to the wrong machine.

User avatar
rpdom
Posts: 16764
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: SSH Permission denied

Sun Jan 25, 2015 8:04 am

Yeah, this line is a bit of a giveaway:

debug1: Remote protocol version 2.0, remote software version OpenSSH_6.2_hpn13v11 FreeBSD-20130515

;)

Return to “Troubleshooting”