21

I am trying to connect to a local IP address via SSH from the terminal. The command is 

ssh -v user@192.168.0.2

But it is not connecting. It keeps giving me the error

"Permission denied (publickey,password)."

I have been searching for ages and just can't find what the issue is. I can connect using the same method via PuTTY on windows and can connect via FileZilla

Full output:

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: Connecting to 192.168.0.2 [192.168.0.2] port 22.
debug1: Connection established.
debug1: identity file /Users/[UserName]/.ssh/id_rsa type 1
debug1: identity file /Users/UserName/.ssh/id_rsa-cert type -1
debug1: identity file /Users/UserName/.ssh/id_dsa type -1
debug1: identity file /Users/UserName/.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.0p1 Debian-4+deb7u2
debug1: match: OpenSSH_6.0p1 Debian-4+deb7u2 pat OpenSSH*
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 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: [Server Host Key]
debug1: Host '192.168.0.2' is known and matches the RSA host key.
debug1: Found key in /Users/[UserName]/.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/[UserName]/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /Users/[UserName]/.ssh/id_dsa
debug1: No more authentication methods to try.
Permission denied (publickey,password).
Peter Mortensen
  • 12,326
harnamc
  • 315

4 Answers4

14

Try to add the key again.

First set PasswordAuthentication yes in file sshd_config at the destination machine, and then do ssh-copy-id user@host, log in, and then it will copy the key over.

Now you can set PasswordAuthentication no (if you want, for extra security), and you should be able to log in automatically.

You could also use your curiosity and check if id_rsa.pub from the source machine is in the authorized_keys file on the destination machine.

Peter Mortensen
  • 12,326
barlop
  • 25,198
7

You probably have set PasswordAuthentication no in /etc/ssh/ssh_config on the machine where you start ssh. This file is used for outgoing ssh connections.

The same setting also exists in /etc/ssh/sshd_config (sshd, not ssh!) of your remote machine for incoming ssh connections. But if this settings were wrong it would also not have worked with putty or with ssh from another computer.

The setting in both files have to be set to PasswordAuthentication yes to make it work.

When you are not an admin or just don't want to change your local /etc/ssh/ssh_config permanently, you can also pass the parameter to the ssh command line:

ssh -o "PasswordAuthentication yes" yourserverip
Michael Dreher
  • 181
4

First run cat $HOME/.ssh/id_rsa.pub on your computer. That will get you a key. Save this key somewhere.

Then open this file by running vim $HOME/.ssh/authorized_keys on the computer that you're are ssh'ing to. Then copy the key in a new line of this file and close it by typing :wq.

You are all set.

Peter Mortensen
  • 12,326
user2393015
  • 141
4

It might be different because it looks like you are connecting to localhost or something (192.168.0.2 or is that just for the question?).

What often solves things like this is to edit the ~/.ssh/known_hosts file and delete the entry for the domain you are connecting to, it will re-prompt you for ssh credentials and avoid problems caused by incorrect "expectations".

beroe
  • 1,255