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

Test SSH config in SourceTree terminal fails

We have a script that tests our user's development environment to make sure everything is set up correctly.  To test that SSH is setup the script runs 

ssh -T

which is straight from Atlassian's trouble shooting page:


For some reason though, one of our SourceTree users fails this test even though their SSH connection to bitbucket is working fine.  They can run git pull or push without and trouble but when they run the command above they get:

$ ssh -T Permission denied (publickey).

Upgrading to SourceTree 3.1.3 and the latest embedded git gave the same result

Any ideas?



1 answer

0 votes
Mike Corsaro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 14, 2019


This probably has to do with any of the following:

  • The path to SSH is not the same as the other machines (check environment variables)
  • The SSH key info is being saved to .gitconfig in another location (I think the way git feeds SSH info to git is different than just running ssh -T). Run the following command to see where all git configurations come from and compare it to the working machines:
    git config --list --show-origin

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events