Skip to end of metadata
Go to start of metadata

If you are having problems with SSH, here are some things you can try when troubleshooting your issues. 

Specific Error Messages

Permission denied (publickey) or No suitable response from remote

When attempting to clone, push or pull over SSH with Git or Mercurial, you receive the message:

OR

You are receiving this message because Bitbucket could not authenticate you with any of the keys that were offered to it by your SSH agent.  To verify this is the case, do the following:

GitMercurial
ssh -Tv git@bitbucket.org
ssh -Tv hg@bitbucket.org

The command tests your connection to Bitbucket as a Git or Mercurial user. It first sees if your SSH Agent has an identity loaded. The command then checks if that private key matches a public key for an existing Bitbucket account. You might have either problem.

The permission denied message can be caused by a couple of factors, but these are the most common.

Your public key isn't loaded into Bitbucket

To check to see if your public key is loaded into Bitbucket, do the following:

  1. Open a browser and log into Bitbucket.
  2. Choose Username > Account from the menu bar. 
    The system displays the Account settings page.
  3. Click SSH keys.
    The SSH Keys page displays. It shows a list of any existing keys.
  4. If you do not have any keys listed, follow Add an SSH key to an account to set one up.

Your identity isn't loaded into your SSH Agent

If your SSH agent doesn't know to offer Bitbucket a key, the connection will fail. To find out what keys your SSH Agent currently is offering, and add them, do the following:

On GitBash, OSX, or Linux

Then, if you don't see your key listed, add it by 

 

On Windows using Pageant

Double-click Pageant to view loaded keys

Click Add Key to add any key not found in the list

You used sudo when attempting the connection

You do not need to use sudo when cloning a repository or any other SSH action with Bitbucket.

Could not open a connection to your authentication agent

You may see this error when trying to use the ssh-add command. Most likely your ssh-agent was not started properly. To start the agent in the GitBash shell, run the following

Then, use the ssh-add command to add your identities.

.bashrc returns unexpected token

If your .bashrc does not launch correctly and you see lines like the following:

line19: syntax error near unexpected token 'then'
line 19: ' if[ $? -eq 0 ]; then '

Then, you might have introduced errors when cutting and pasting from a browser. We have seen this error when users use the Chrome browser. Try another such as Firefox.

General SSH troubleshooting

Use this section for general SSH troubleshooting.

ssh -T connection test (GitBash/Mac OSX/Linux)

You can use the ssh -T command to test the Mercurial (hg) or Git (git) connection to Bitbucket. The command below illustrates how to test a Mercurial (hg) connection to Bitbucket:

$ ssh -T hg@bitbucket.org
Permission denied (publickey).

If you don't have any keys loaded in the agent, the response is as illustrated above.

A successful response to a Mercurial connection looks like the following:

$ ssh -T hg@bitbucket.org
conq: logged in as tutorials.

You can use git or hg to connect to bitbucket. Shell access is disabled.

Of course, you can also test the Git connection with the ssh -T git@bitbucket.org command structure.

Using ssh verbose mode to track down problems

You can use the -v (verbose) flag with ssh to track down problems with your connection. What happens if you receive a Permission denied (publickey) error but you verified your key is loaded both on your local system and into your Bitbucket account? This happened to me recently.

Running the verbose command:

Output showing the error:

myhost:~ manthony$ ssh -v hg@bitbucket.org
OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /Users/manthony/.ssh/config
debug1: Applying options for bitbucket.org
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug1: Connecting to bitbucket.org [172.16.10.101] port 22.
debug1: Connection established.
debug1: identity file /Users/manthony/.ssh/manthony type 1
debug1: identity file /Users/manthony/.ssh/manthony-cert 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.6
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 zlib@openssh.com
debug1: kex: client->server aes128-ctr hmac-md5 zlib@openssh.com
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 /Users/manthony/.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_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/manthony/.ssh/manthony
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).

In this run, the public key manthony was offered. It failed, the system then tried to use the default key and again failed. If the proper key is offered but fails, check and make sure the key is uploaded to your account. If the key is in the account but it is still failing, try uploading it again. You can also try another key.

If your key isn't offered, make sure the key exists on the local system you are using to connect. Make sure your key is loaded into the key agent. You can do this via a .ssh/config file or manually loading it into the SSH agent with ssh-add. To test if the key is loaded, with ssh-add run the ssh-add -l command. Finally, try recreating the key and uploading it again.

Output showing success:

myhost:~ manthony$ ssh -v hg@bitbucket.org
OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /Users/manthony/.ssh/config
debug1: Applying options for bitbucket.org
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug1: Connecting to bitbucket.org [172.16.10.101] port 22.
debug1: Connection established.
debug1: identity file /Users/manthony/.ssh/manthony type 1
debug1: identity file /Users/manthony/.ssh/manthony-cert 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.6
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 zlib@openssh.com
debug1: kex: client->server aes128-ctr hmac-md5 zlib@openssh.com
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 /Users/manthony/.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 serverhg
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/manthony/.ssh/manthony
debug1: Remote: Forced command: conq manthony
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: read PEM private key done: type RSA
Identity added: /Users/manthony/.ssh/manthony (/Users/manthony/.ssh/manthony)
debug1: read PEM private key done: type RSA
Connection closed by 172.16.10.101

 

Is the ssh-agent running?

On Windows make sure Pageant is running in your system tray:

 

For GitBash, Mac OSX, or Linux:

Open a terminal window and enter the ps -e | grep [s]sh-agent command to see if the agent is running:

myhost:~ manthony$ ps -e  | grep [s]sh-agent
 9060 ??         0:00.28 /usr/bin/ssh-agent -l

If the agent isn't running, start it manually with the following command:

myhost:~ manthony$ ssh-agent /bin/bash

Is the identity you want to use loaded?

On Windows, double-click Pageant and check which key is loaded:

 

On GitBash/Mac OSX/Linux, the the following:

To list the loaded entities:

$ ssh-add -l
2048 4c:80:61:2c:00:3f:9d:dc:08:41:2e:c0:cf:b9:17:69 /Users/manthony/.ssh/workid (RSA)
2048 7a:9c:b2:9c:8e:4e:f4:af:de:70:77:b9:52:fd:44:97 /Users/manthony/.ssh/personalid (RSA)

To load an identity:

ssh-add ~/.ssh/identity

With ssh-agent management Bitbucket uses the first key in the list. If you are still having problems, try removing all but the identity you want to connect with, to do this:

ssh-add -d ~/.ssh/identity

Using a single key without a config file (Mac OSX and Linux)

Instead of the config file, you can use the ssh-add command to manually load an identity into the ssh-agent management program.

$ ssh-add ~/.ssh/personalid
Enter passphrase for /Users/manthony/.ssh/personalid: 
Identity added: /Users/manthony/.ssh/personalid (/Users/manthony/.ssh/personalid)
myhost:~ manthony$ 


Use the ssh-add command to list the keys that the agent is managing:

$ ssh-add -l
2048 4c:80:61:2c:00:3f:9d:dc:08:41:2e:c0:cf:b9:17:69 /Users/manthony/.ssh/workid (RSA)
2048 7a:9c:b2:9c:8e:4e:f4:af:de:70:77:b9:52:fd:44:97 /Users/manthony/.ssh/personalid (RSA)

In this instance, the Bitbucket server always uses the first key it encounters. So, this is not a good technique to use for multiple identities.

You can remove an identity from the agent using ssh-add with the -d flag. You can also set an identity to expire from the list with the ssh-add command.

ssh-agent on GitBash

If your key is uploaded and you are still having trouble connecting. Make sure you are not running multiple versions of the ssh-agent. To do this, enter the following at the GitBash command line:

$ ps
  PID PPID PGID  WINPID TTY UID STIME COMMAND
  5192  1 5192  5192 ? 500 19:23:34 /bin/ssh-agent
  5840  1 5840  5840 con 500 08:38:20 /bin/sh
  6116 5840 6116  1336 con 500 08:38:22 /bin/ps

Kill all the agents and restart it. Some users find that the ssh-agent binds to the terminal window they use effectively blocking any further action with SSH. To avoid this problem, run the program as follows:

$ eval 'ssh-agent'

This runs the process and also forks it from the terminal window. 

Operation timed out

You can receive a message similar to the following:

A timeout means that your computer was unable to reach Bitbucket.  This is likely due to something in your own network.  For example, your network administrator may have a firewall rule that blocks the connection.  Talk to your network administrator to resolve the issue. 

Mercurial (or TortoiseHg) on Windows with PuTTygen/Pageant

Use this section if you are working in Microsoft windows with TortoiseHG and managing your keys with PuTTYgen/Pageant.

remote: No supposted authentication methods left to try!

You can get this error, for example, when cloning a repository:

Check the following:

  • Pageant is running and has a key loaded.
  • You have added the corresponding public key into your Bitbucket account.

pushing a new repository is slow or hangs

It could be you have not configured Mercurial compression. On Windows do this:

When sending or retrieving data using SSH, Git does compression for you. Mercurial does not automatically do compression.  If you are using Mercurial, you should enable SSH compression as it can speed up things drastically, in some cases. To enable compression for Mercurial, do the following:

  1. Start the TortoiseHg Workbench.
  2. Select File > Settings.
  3. Make sure you have the global settings tab selected.
  4. Press Edit File.
  5. Add the following line to the UI section:

    ssh = "TortoisePlink.exe" -ssh -2 -batch -C

    When you are done the file should look similar to the following:

    [ui]
    # Name data to appear in commits
    username = Mary Anthony <manthony@atlassian.com>
    ssh = "C:\Program Files\TortoiseHg\TortoisePlink.exe" -ssh -2 -batch -C
  6. Press Save to store your settings and close the file.
  7. Press OK to close the settings dialog.

 

In Mac OSX or Linux do this:

When sending or retrieving data using SSH, Git does compression for you. Mercurial does not automatically do compression.  You should enable SSH compression as it can speed up things drastically, in some cases. To enable compression for Mercurial, do the following:

  1. Open a terminal window.
  2. Edit the Mercurial global configuration file (~/.hgrc).
  3. Add the following line to the UI section:

    ssh = ssh -C

    When you are done the file should look similar to the following:

    [ui]
    # Name data to appear in commits
    username = Mary Anthony <manthony@atlassian.com>
    ssh = ssh -C
  4. Save and close the file.

27 Comments

  1. Anonymous

    I was having hard times to make it work with ssh on Windows. I've tried literally everything. It gives me the following error:

    Disconnected: No supported authentication methods available (server sent: publickey) 

    There's no way to debug the problem since TortoisePlink seems to ignore -v command line option.

    Finally I gave up and set up using genuine plink and pageant from putty distribution.

    1. Anonymous

      I use mercurial for main job (over vpn) and also I have repo on bitbucket. I've configured mercurial.ini for use with my office mercurial server, but unfortunately these settings didn't work with bitbucket repos. I receve "remote: No supposted authentication methods left to try!"

      Finally I found a workaround. In the local clone of repo that resides on bitbucket open the myrepo/.hg/hgrc file and add the following:

      [ui]
      ssh = "TortoisePlink.exe" -ssh -2

      This will override settings from mercurial.ini. Note that there are no -batch -C parameters unlike described at Set up SSH for Mercurial.

      Also, don't forget to run pageant that comes with tortoisehg (when i tried to use that one from putty.org, TortoisePlink did't recognize it).

      1. Anonymous

        I forgot the Pageant, and after running it and adding my key, it worked for me!

  2. Anonymous

    Thanks for the great help page.  I found what I needed here!

    1. Super! I'm glad to know it helped.

  3. Anonymous

    I installed Mercurial today and it is taking me forever to push my first repository (~45 min), I'm sure it has to do with compression.  This example is only for TortoiseHg, which I didn't download, as I went the Python 2.7 package version.  I'm assuming the general idea applies that you have to set the ssh in the Mercurial.ini file, however the syntax is probably different.

    What I have set up currently in the .ini file is this:

    ssh  = "C:\Users\MyName\ssh\plink.exe" -ssh -i "C:\Users\MyName\ssh\default_rsa.ppk"

    Is there something wrong with this?  All the other examples using Tortoise include -C or -2, and I'm not sure of their purpose.  

     

    1. Anonymous

      It also just came up with the prompt:

      The server's host key is not cached in the registry. You have no guarantee that the server is the computer you think it is. The server's key fingerprint is: ssh-rsa 1024 7b:e5:6f:a7:f4:f9:81:62:5c:e3:1f:bf:8b:57:6c:5a If you trust this host, hit Yes to add the key to PuTTY's cache and carry on connecting. If you want to carry on connecting just once, without adding the key to the cache, hit No. If you do not trust this host, hit Cancel to abandon the connection.

      However it happened really fast and I wasn't able to select y/n and it aborted...I know this happens as a first time SSH verification thing, but I'm not sure why it's cancelling out so fast.  I'm so confused!

      1. Hi, I'm sorry you are having problems. Please file a ticket with support@bitbucket.org so we can help you more directly.  When you file your ticket, please provide:

        • your repository name
        • your account name
        • the name an version of your client software (TortoiseHg version XXX)

        Regards,

        Mary

  4. Anonymous

    Autostart Pageant before commiting to Bitbucket?

    On Windows: Is there a way to auto-start Pageant and have it load the keyfile automatically when TortoiseHg-Workbench is started?

    I find it a bit of a nuisance, to manually have to start Pageant and load the key, before commiting to Bitbucket.

    Regards,
    Reinhard

    1. Anonymous

      PS: not throwing Pageant into Autostart-Folder, which would start it on every logon to Windows - just with starting Workbench

       

    2. Reinhard,

      The PuTTY 6.0 user manual describes how to auto-start Pageant with a key:

      http://the.earth.li/~sgtatham/putty/0.60/htmldoc/Chapter9.html#pageant-cmdline-loadkey

      If you want to start it with the Workbench, you could probably create a .bat file that loads the key and starts workbench.  

      Cheers,

      Mary

  5. Anonymous

    I have run throuhg all the troubleshooting tips and have made a successful connection with ssh -v git@bitbucket.org but when I try to do a pull  I received 

    Permission denied (publickey).
    fatal: The remote end hung up unexpectedly

    Any assistance would be wonderful. Thanks

    1. I'm sorry you are having problems.  It is hard to tell what the problem is without knowing which repository you are trying to pull and your BB username.  You should file a ticket with support@bitbucket.org and send this information along with the output of the ssh -v command.

  6. Anonymous

    How do you configure SSH to use a proxy? (Or can it even be done?)

    1. We don't document how to do this as it is network specific. A quick google of "ssh through a proxy" reveals a lot of hits on this topic.

  7. Anonymous

    Running $ ssh -T git@bitbucket.org I get a message like:

    conq: logged in as USERNAME.

    You can use git or hg to connect to Bitbucket. Shell access is disabled.

    But I am not that username.

    1. We don't allow you to SSH under your own username to our site.  When you use SSH with BB you are either going through the hg or git service.  You can see this by looking at the formats of the URLs for these:

       SSH URL formatHTTPS URL format
      Mercurialssh://hg@bitbucket.org/accountname/reponame/

      https://accountname@bitbucket.org/accountname/reponame

      Git

      git@bitbucket.org:accountname/reponame.git

      or

      ssh://git@bitbucket.org/accountname/reponame.git

      https://accountname@bitbucket.org/accountname/reponame.git

      In the SSH format, the accountname appears after git@bitbucket.org or hg@bitbucket.org. In HTTPS format, the accountname before git@bitbucket.org or hg@bitbucket.org.

      1. Anonymous

        same problem with me. i have different accountname, but on doing

        ssh -vT git@bitbucket.org 

        i have particular this line

        debug1: Remote: Forced command: conq username:<username> 

        this username is not mine.

         

        how can i change this? 

  8. Thanks a lot for the detailed explanations how to link bitbucket with the local GIT bash via ssh!

    Unfortunately, while my ssh connection seems to work,

     Click here to expand problem description...

    $ ssh -Tv git@bitbucket.org
    OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
    debug1: Reading configuration data /h/.ssh/config
    debug1: Applying options for bitbucket.org
    debug1: Connecting to bitbucket.org [207.223.240.182] port 22.
    debug1: Connection established.
    debug1: identity file /h/.ssh/id_rsa 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 'bitbucket.org' is known and matches the RSA host key.
    debug1: Found key in /h/.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: Offering public key: /h/.ssh/id_rsa
    debug1: Remote: Forced command: conq username:sscherer
    debug1: Remote: Port forwarding disabled.
    debug1: Remote: X11 forwarding disabled.
    debug1: Remote: Agent forwarding disabled.
    debug1: Remote: Pty allocation disabled.
    debug1: Server accepts key: pkalg ssh-rsa blen 277
    debug1: Remote: Forced command: conq username:sscherer
    debug1: Remote: Port forwarding disabled.
    debug1: Remote: X11 forwarding disabled.
    debug1: Remote: Agent forwarding disabled.
    debug1: Remote: Pty allocation disabled.
    debug1: Authentication succeeded (publickey).
    debug1: channel 0: new [client-session]
    debug1: Entering interactive session.
    conq: logged in as sscherer.

    You can use git or hg to connect to Bitbucket. Shell access is disabled.
    debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
    debug1: channel 0: free: client-session, nchannels 1
    debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.3 seconds
    debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
    debug1: Exit status 0

     

    I cannot push changes via ssh (it does work via https). I do get the following error message:

    $ git push
    FATAL ERROR: Disconnected: No supported authentication methods available (server
     sent: publickey)
    fatal: Could not read from remote repository.

    Please make sure you have the correct access rights
    and the repository exists.

    Any idea what may going on here?

    Thanks!

    1. It appears you don't have permissions on the repository you are pushing to.  Check where you push is going by listing your remotes:

      1. Change directory to the root of your repo.
      2. List the remotes:

        $ git remote -v
        origin	https://atlassian_tutorial@bitbucket.org/atlassian_tutorial/helloworld2.git (fetch)
        origin	https://atlassian_tutorial@bitbucket.org/atlassian_tutorial/helloworld2.git (push)
      3. Verify you have access to the repository listed in the remote.

      If you need to se a remote the syntax is:

      git remote add [shortname] [url]:
  9. Thanks for your quick response!

    Alas, this didn't solve the problem, but I did manage to sort things out with the help of a colleague. It seems that there was an interference of the git-provided ssh with my pre-existing installation of putty.

    I did uninstall git and putty, and then install anew first git, then putty, and now everything works fine.

    The Git Release Notes of the version that I did install on my computer (Git-1.8.3-preview20130601) say that “If configured to use Plink, you will have to connect with putty first and accept the host key.” So, at hindsight, it may have been sufficient to either open a putty connection to bitbucket.org before starting git, or maybe to remove the bitbucket ssh host key from the putty registry entry at HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys, but I did not check out that.

    Anyway, thanks for your help and time, and for the great tutorial!

    1. Super. Glad you are up and running!

  10. Anonymous

    Hi! In my team there was also few fellows with Windows machines and Git-Bash and they had this same error:

    No supported authentication methods available (server sent: publickey).

    After much debugging and hacking it turns out that the general situation with us and several other posts in this thread is there is 2 installations of ssh available in your machine and you have created and uploaded your keys with one and use git with the other.

    TortoiseGit defined an environment variable GIT_SSH with full path to your ssh client 'ssh.exe'. It tells git which ssh to use.  Defining that correctly to point to git-bash own ssh.exe resolves to conflict well.  Defining it in .bashrc effects only operations inside git-bash, windows environment variable is visible to all windows processes (after re-login(smile)). You need to consider your situation carefully if you want to use git-bash for command line and TortoiseGit for Windows Explorer: You need both GIT_BASH in .bashrc and TortoiseGit version in Windows environment variable AND you need to create and upload ssh-keys with both ssh clients to your BB account. (I do not even want to dive into the IDE specifics here...)

     

  11. Anonymous

    I encountered the issue "Could not open a connection to your authentication agent"

    If it can help, I fixed it using :

    eval "$(ssh-agent)"

    The given command

    eval `ssh-agent`

    didn't woks for me...

  12. Another gotcha, ensure PublickeyAuthentication is not disabled in the ~/.ssh/config file. I had an old config file (result of copying my .ssh folder from old account  to new one), in which I had explicitly disabled PublicKeyAuth and X11 forward for new hosts using something like:

     ~.ssh/config:
    ...some known hosts...
    Host *
        PubkeyAuthentication = no
        ForwardX11 = no

    This would prevent hg / ssh to offer the publickey and I would get a public key denied error message. Removing these lines (or adding an explicit entry for bitbucket.org) fixed the issue.

     

  13. Anonymous

    Hi

    i tried to solve the following problem but nothing worked:

    'You can use git or hg to connect to Bitbucket. Shell access is disabled.'

     

    please help.