Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Github Permission denied (publickey)


Hi, I downloaded SourceTree 2.7.6 today, and encountered below error, so I am denied access to all remote git operations with sourcetree.

git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree fetch origin Permission denied (publickey).

fatal: Could not read from remote repository.

 Please make sure you have the correct access rights

and the repository exists.

 FYI, my github account is added in SourceTree with Oauth, my ssh keys are well setted in local directory and in github account,  and I can do all remote git operation in terminal using commands.

Please help me with this issue, Thank you!




problem solved after adding the key to ssh agent using below command

$ ssh-add -K ~/.ssh/id_rsa


 after some experiment I think the private key must be named  id_rsa for SourceTree to work, which is an inconvenience and should be solved by sourcetree developers!!!!!!!

2 answers

What you need to do is set it in the config file in your .ssh folder to use the right key when talking to the right domain.  'config' is just a plain text file that the SSH Agent uses to know which keys to use where.

In the case of GitHub you should have something that looks like this:

Host GitHub
    IdentityFile /<path>/<to>/.ssh/<YOUR KEY TO USE>
    UseKeychain yes
    AddKeysToAgent yes

You can then set different keys to use with different domains and servers.

The other thing that is critical is to make sure you add the key you create to the Agent's list of keys like you did in your edit.

- Grant

As a followup to the answer above, anytime I go to a repo on (HostName) it will use the key I provide a path to (IdentityFile) to make the SSH connection.

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 31, 2018

Sourcetree will respect whatever keys are loaded in your user environment and the configuration file contents, it isn't doing anything special beyond that. The SSH key management we introduced will generate and configure SSH keys for each service + account and use that if configured, otherwise it will default to id_rsa. Unfortunately macOS has a habit of forgetting loaded SSH keys which is a quirk introduced in 10.12.

Brian Ganninger
Senior Mac Developer, Sourcetree

Thanks for the reply. Unfortunately, I couldn’t find where to configure the ssh keys. There are no ssh key management options in the preferences&settings.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events