Issue #3214 resolved
Former user created an issue


I'm new with Bitbucket. I created a git repository then cloned it successfully !

Since I tried to create a ssh key and upload it, I can not connect to the repository anymore ...

I get this message:

$ git clone Cloning into repo... Permission denied (publickey). fatal: The remote end hung up unexpectedly

I also tried {{{ssh -v}}} and i got :

{{{ OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007 debug1: Connecting to [] port 22. debug1: Connection established. debug1: identity file /c/Users/username/.ssh/identity type -1 debug1: identity file /c/Users/username/.ssh/id_rsa type -1 debug1: identity file /c/Users/username/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc 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: Host '' is known and matches the RSA host key. debug1: Found key in /c/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: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: /c/Users/username/.ssh/identity debug1: Trying private key: /c/Users/username/.ssh/id_rsa debug1: Trying private key: /c/Users/Maxime/.ssh/id_dsa debug1: No more authentication methods to try. Permission denied (publickey). }}}

Can someone help me ? Is there any way to have the repository access without key needed ?

Thanks, Maxime.

Comments (4)

  1. Log in to comment