Sourcetree for Windows keep telling me the "server refused our key"

Using the latest version of Sourcetree ( connecting to both GitHub and BitBucket i keep getting an error message when trying to talk to the server with Sourcetree. The error I get is:

Server refused our key
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.

I setup a PuTTY entry with the key (the .ppk containing my SSH key) and I was able to SSH successfully to bitbucket with the key, loosly following this guide. (I did this from Git Bash as well with the private key in id_rsa format and it worked too).

(will answer it myself, as it took a number of hours of playing before I got it)

2 answers

1 accepted

What my problem ended up being was this:

I've used PuTTY for a long time on my computer (long before Sourcetree). PuTTY saves its settings in your registry, so the settings from the "Default Settings" entry in PuTTY are loaded when Sourcetree / Pageant attempt to connect to BitBucket. Specifically my problem stemmed from a private key being set under:

Connection > SSH > Auth, in the "Private key file for authentication" box.

Once I removed that key from that box (just deleted the text), and saved the Default Settings session in PuTTY, Sourcetree started to behave properly. This was caused because Pageant will seem to only use the SSH key you have in that box, even if you have a lot of other SSH keys added to Pageant.

Debugging Tip:

How I ended up discovering this issue was using the plink tool from PuTTY. You can download it from PuTTY's site. What I ended up doing was:

  1. Downloading plink
  2. Stick it into an easily accessible directory
  3. Open a DOS cmd window (cmd.exe or something similar)
  4. "cd" to where plink.exe is
  5. Run the command:
    1. plink.exe -v
  6. You will get verbose output of what putty does during it's connection and you can see what SSL key is used during the handshake.

If the connection is unsuccessful, the last few lines of the output will look something like this:

Offered public key
Server refused our key
Server refused our key
Disconnected: No supported authentication methods available (server sent: publickey)
FATAL ERROR: Disconnected: No supported authentication methods available (server sent: publickey)

If the connection is successful, you should see something like this:

Access granted
Opened channel for session
Server refused to allocate pty
Started a shell/command
conq: logged in as kyrra.

You can use git or hg to connect to Bitbucket. Shell access is disabled.
Server sent command exit status 0
Disconnected: All channels closed

Glad you figured this out, and thanks for posting such a comprehensive reply. It's useful that PuTTY lets you configure things at a finer level via this interface (handy for specifying aliases to specific setups for example) but it can definitely be a pain if you have some old settings lying around. The SSH key setting, either per alias/session or in the Default Settings overrides any other choice of key with no fallback so your diagnosis makes sense, although I can imagine it was a pain to locate.

You are a genius my problem was also the default settings specifically the port that was other than 22

Thanks! This was my issue too.

I am having a similar issue. I'm getting that error message above, but I don't even use PuTTY. Any help in how to fix this would be appreciated.



SourceTree for Windows up to 0.9.1 actually only supports PuTTY as the SSH implementation. If you have OpenSSH keys in ~/.ssh instead then you can import them into PuTTY format, there's information on how to do this in the FAQ: (at the bottom, 'How do I set up SSH keys')

We have a update pending which also allows the use of OpenSSH directly, although we still highly recommend PuTTY since it's more Windows-native and not designed primarily for terminal use like OpenSSH.

Suggest an answer

Log in or Join to answer
Community showcase
Jason Wong
Published Tuesday in Agility Beta

Welcome to agility

Every team in the world is unique, and so   Atlassian believes   that each and every team's best way of working  needs to  be molded to their unique circumstances  – ...

429 views 6 16
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot