Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Permission denied (publickey) (sourcetree mac)

Pushing to git@bitbucket.org:(my repo).git

git@bitbucket.org: Permission denied (publickey).

fatal: Could not read from remote repository.

 

Please make sure you have the correct access rights

and the repository exists.

I suddenly started getting this, if I try to change everything thing back to default and try again, I get "device not configured".

 

This suddenly started happening after upgrading to High Sierra

2 answers

12 votes
Manju Atlassian Team Apr 10, 2018

Please check if the ssh-agent has your keys loaded. If not, please add them to the agent. 

Run below commands in terminal to do so,

To check if keys are loaded:

ssh-add -l

To add keys to agent:

ssh-add <path_to_key>

more like,

ssh-add ~/.ssh/id_rsa

Key in the passphrase used while generating the ssh key and you should be good to go.

It appears this isn't the solution, there's a bug in the latest version of sourcetree.

Downgrading to the previous stable build fixed everything.

Like # people like this

@hawkenking can you tell which version does work for you?

Manju Atlassian Team May 24, 2018

Could you please confirm what version you used earlier and what was the result of running those commands on your machine?

It helps me.
Thx a lot.

What I did just yesterday to fix this problem:

1. Create "config" file in ~/.ssh

2. Put in this config:

Host = *
UseKeychain yes
AddKeysToAgent yes
IdentifyFile path/to/your/private/key
IdentityFile path/to/your/another/private/key

After that authentication goes smoothly(with help of "ssh-add -K identity"). This seems to be a change related to macOS update: required for Sierra or High Sierra. 

IdentityFile, not IdentifyFile

Using this on Mojave fixed my problem. I thought those identities got added automatically but I guess that's wrong. Thanks for the suggestion!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

3,250 views 4 5
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you