SourceTree 2.4 claims problem with ssh

Was running version 2.3.2 (75) on Mac OS 10.12.1 just fine.  I have repositories on github and bitbucket.  After upgrading to SourceTree 2.4, I immediately get this error:

There is an issue with your SSH configuration

The SSH configuration for your GitHub account ((null)) is incomplete. Please edit this account to generate a new SSH key.

When I click the Show Accounts button, no accounts are visible.

If I pull the older version 2.3.2 out of the trash and run it, things are working again.

6 answers

same error message in version Version 2.4 (93)

Hi. I have the similar issue here.
After upgrade to latest Sourcetree v2.4 (90) i get following error:
image2016-12-21 17:15:56.png

On Accounts tab in preferences app ask me to generate new keys for each account.

image2016-12-21 17:28:8.png

Seems like Sourcetree don't see my existing ssh key.

image2016-12-21 17:32:59.png

Is it possible to set my own SSH key?

I have the same problem, then if I generate a key, then add it to Github in my case it seems not to be working!?

0 votes
Gary Sackett Atlassian Team Jan 12, 2017

Hi Everyone,

With 2.4 we added an option to have  SourceTree manage your SSH key per account - it generates the key and optionally adds to your SSH configuration. The warning just indicates when that isn't present. We did not detect existing SSH configurations and map them to accounts you've set up in ST.

Existing/configured SSH users should simply ignore the feature essentially, just set the protocol to SSH and continue on past the error message.  However, users should not be receiving the error message on a regular basis, which they are currently with 2.4.  A new bug has ben created, and assigned to a developer at  Please follow this bug for the latest updates on a fix.


Thanks for the update Gary. Looking forward to using v2.4 after this bugfix.

Added my 'vote' to JIRA.

Every time I open a window for a repository I get the warning message. Which sucks when I am opening and closing 20 repos on a daily basis.

Why has the option to use our own keys been removed? I'd prefer to use my own existing keys, rather than generate all new keys.

Suggest an answer

Log in or Sign up to answer
Community showcase

Scrum Roles Explained: the Do's and the Don'ts

Hello Community,  Today we are going to talk about the three Scrum Roles. There is the Development Team, the Scrum Master and the Product Owner. In my opinion these three are all really impo...

38 views 0 4
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