Source Tree (2.7.152) BitBucket authentication issue

I have connected Source Tree (2.7.152) to BitBucket but since most recent update I have authentication issues. Each time when I try to pull or to push is telling me that credentials are invalid because of third party software and I need to go to Preferences -> Accounts and re-authenticate my account again.

Any clue what is going on?

Thanks

6 answers

0 vote

What third party software is being referenced?

Pushing to https://me@bitbucket.org/mydev/repo.git

remote: Invalid username or password. If you log in via a third party service you must ensure you have an account password set in your account profile.

fatal: Authentication failed for 'https://me@bitbucket.org/mydev/repo.git/'

Completed with errors, see above

I'm getting the same:

"Pushing to git@gitlab.com:*********/********.git
Permission denied (publickey).
fatal: Could not read from remote repository."

"Please make sure you have the correct access rights and the repository exists."

I have the same issue after updating. On Mac OS Sierra. Have tried resetting my password.

Strangely, I get the same with GitHub Desktop but not when pushing directly from the terminal. Could it somehow be GUI related?

I fixed this by deleting the whole Sourcetree folder in Library/application support/sourcetree and re-installing. Prior to that I had changed my password, which didn't work, but maybe it had an effect (in case someone tries this, and the first step doesn't solve it by itself).

 

This was on Sourcetree 2.7 on Mac OS Sierra.

0 vote
Ben Cato I'm New Here Feb 19, 2018

POS F'ing Sourcetree. This happens with almost every update. Everything is/has been fine, install the latest update, all of my authentications fail, constantly have to enter username/password. Here's a great tip that I just found: Don't use Sourcetree. Switch to command line (which I'm still not a fan of) or GitKraken. 0% issues. I hate you, Sourcetree. POS. Gone.

Looks like this is the same ssh issue which many folks are facing. 

Please check if your ssh keys are added to the agent by running below command in terminal

ssh-add -l

If none are listed, please add the key to the agent using below command,

ssh-add <path_to_key>

more like

ssh-add ~/.ssh/id_rsa

This should fix your problems. 

If you want to learn more about why this happens and how to fix this permanently, read this Technical Note from Apple

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Brian Ganninger
Published Jan 23, 2018 in Sourcetree

Tip from the team: workflow and keyboard shortcuts

Supported Platforms macOS Sourcetree has a lot to offer and, like many developer tools, finding and using it all can be a challenge, especially for a new user. Everyone might not love ...

798 views 0 4
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you