Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have been trying to log on to my Azure server's Virtual Machine that's running on Ubuntu 12.04 LTS for hours. I would appreciate it a lot if someone could help me.

  1. I generated new ssh keys

    ssh-keygen -t rsa -C "" ssh-add ~/.ssh/id_rsa

  2. I generated a .pem file

    openssl req -x509 -new -days 365 -key id_rsa -out id_rsa.x509req.pem

  3. I tried to log in with ssh

    ssh -vvv

But it asks for a password, but I didn't input any password when creating the keys.

This is the log

maxuimbp:.ssh max$ ssh -v
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 [] port 22.
debug1: Connection established.
debug1: identity file /Users/max/.ssh/id_rsa type 1
debug1: identity file /Users/max/.ssh/id_rsa-cert type -1
debug1: identity file /Users/max/.ssh/id_dsa type -1
debug1: identity file /Users/max/.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 none
debug1: kex: client->server aes128-ctr 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 3f:44:3f:91:dd:7b:15:fb:5f:c7:64:14:df:bc:3f:21
debug1: Host '' is known and matches the RSA host key.
debug1: Found key in /Users/max/.ssh/known_hosts:2
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_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/max/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Offering RSA public key: /Users/max/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /Users/max/.ssh/id_dsa
debug1: Next authentication method: password's password:

I thought I did everything perfectly. Does anyone know why this is happening to me?

share|improve this question
Did you happen to add the public key to the authorized keys on the target? – Falcon Momot Jun 14 '14 at 8:45
up vote 2 down vote accepted

It's not asking for a password for the key, it's asking for a password for the account your trying to log on to as the key based methods have failed.

share|improve this answer
Thank you lain, the problem was that I was doing ssh but I should've done ssh – Maximus S Jun 14 '14 at 9:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.