Issue #3636 resolved

Can't clone new repository

eyalgu
created an issue

I'm trying to clone my newly created repository, with no luck: Using PuTTY I run this command in a new directory:

hg clone ssh://hg@bitbucket.org/eyalgu/ran-tenenbaum

and I get: [dschubba]$ hg clone ssh://hg@bitbucket.org/eyalgu/ran-tenenbaum remote: Permission denied (publickey).

Can you please help? Thanks, Eyal

Comments (6)

  1. Atlassian Tutorials

    Hi Eyal,

    I'm sorry you are having problems. It sounds like your public key is not set up properly. Make sure your public key is uploaded to your bitbucket account. There are instructions for doing that in the tutorial here:

    http://confluence.atlassian.com/display/BITBUCKET/Set+up+SSH+for+Mercurial

    If you are still having problems, you should check our SSH Troubleshooting page here:

    http://confluence.atlassian.com/display/BITBUCKET/Troubleshooting+SSH+Issues

    If none of this resolves your issues, please send us the output from the following command:

    ssh -v hg@bitbucket.org

    Regards,

    Mary

  2. eyalgu reporter

    Thank you for your reply. However, my 'hg' commands work ok for my domain www.eyalg.com, whereas cloning the new repository as mentioned above - fails in the same PuTTY session.

    Here's the output from ssh -v hg@bitbucket.org

    [dschubba]$ ssh -v hg@bitbucket.org OpenSSH_5.1p1 Debian-5, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to bitbucket.org [207.223.240.182] port 22. debug1: Connection established. debug1: identity file /home/eyalg/.ssh/identity type -1 debug1: identity file /home/eyalg/.ssh/id_rsa type -1 debug1: identity file /home/eyalg/.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_5.1p1 Debian-5 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 'bitbucket.org' is known and matches the RSA host key. debug1: Found key in /home/eyalg/.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: /home/eyalg/.ssh/identity debug1: Trying private key: /home/eyalg/.ssh/id_rsa debug1: Trying private key: /home/eyalg/.ssh/id_dsa debug1: No more authentication methods to try. Permission denied (publickey).

  3. Log in to comment