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

SourceTree Forbbiden, but ssh -Tv -l >>username<< works

I have multiple Bitbucket accounts. One is a personal account, which is working perfectly. The other is a work account where I have a personal profile as well as a team profile which owns the repo in question.


As of last night I am unable to get Sourcetree to authenticate with the work repo. I was getting the Atlascode VSCode extension up and running when everyone broke.


My personal account has an ssh key pair configured which works from the terminal (ssh -Tv as well as pushing, pulling & fetching via Sourcetree.

My work account has an ssh keypair configured on the personal work account. That account has admin rights to the team account and the repo. I am able to run ssh -Tv -l >>work_username<< from terminal successfully, but any action performed through Sourcetree yields the error
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists."


I have also ensured ~/.ssh/config has the correct host settings. I have been trying to fix this for hours now and I am simply out of ideas.

1 answer

1 accepted

0 votes
Answer accepted

Of course after posting this I figure it out... Despite not requiring this configuration in the past (with exactly the same setup as I have now) I essentially started over again and setup my ssh keys manually in terminal by following this guide 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events