After upgrading to Sourcetree 4.1.8 I am unable to authenticate to remote repos

Paul Ullrich
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!
July 21, 2022

I recently took an update to Sourcetree 4.1.8 and ever since I took the update, I am unable to pull or clone from any of my repos. I always get the following message:

remote: Bitbucket Cloud recently stopped supporting account passwords for Git authentication.

remote: See our community post for more details: https://atlassian.community/t5/x/x/ba-p/1948231

remote: App passwords are recommended for most use cases and can be created in your Personal settings:

remote: https://bitbucket.org/account/settings/app-passwords/

fatal: Authentication failed for '<url of repo>'

I did get an app password generated and stored it in my keychain on my mac, but it still prompts me for the password each time I do a pull (four times actually) and the password is rejected as invalid each time in the log.

As the only developer on my team now, this is a pretty inopportune time to have a complete and utter failure of the development process.

1 answer

0 votes
Paul Ullrich
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!
July 21, 2022

Answering my own question, but I uninstalled and reinstalled Sourcetree, wiped out my stored passwords pertaining to bitbucket.org, wiped the repos from local, and then was able to pull from remote successfully.

What I THINK happened was that since the last time I worked on the repo, another team member had moved it. So when I tried to authenticate with the new app passwords, though I was getting a valid "authentication failed" message, it wasn't anything to do with my password or the new app passwords implementation, but that the repo itself was not where I was checking and therefore couldn't be pulled. The messaging from bitbucket/sourcetree was fairly confusing in this regard, since it mostly was pointing me to follow down a rabbit hole of password configs.

tl;dr: user error. Strong start for me in this community!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events