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!


Only the first SSH key in Tools->Options->SSH Client Configuration is used when pushing to remote

Dan Swain
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Nov 13, 2023

In the SSH Key field of the SSH Client Configuration, I have inserted two keys separated by semicolons (like this:  path/to/first/key; path/to/second/key;).  All of my repos use either one or the other of these two keys.  Both keys have passphrases on them.  When I load SourceTree (for Windows), it prompts for the passphrase for each key, and after the passphrases are entered, the keys are loaded successfully.  When I push to a remote Bitbucket repo, SourceTree only ever uses (i.e., offers to BitBucket) the first key in the SSH Key field.  If I am unable to push, it is because the SSH key of the repo that is being pushed to is not the first one in the SSH Key field.  If I switch the order of the two keys in the SSH Key field, I am again prompted to enter the passphrases for the keys when I close the Options dialog.  With the order of the two keys switched, I am then able to push changes to the remote repo.  Should there only ever be one key in the SSH key field?  If so, then I don't think it should process all key entries in the field when the Options dialog is closed (that is, it shouldn't ask prompt for passphrases on all keys in the field).  If > 1 key IS allowed in the SSH Key field, then is this a bug that Sourcetree only ever offers up the first key when it is attempting to connect to a remote repo?

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events