nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Getting "fatal: Authentication failed for..." error

bbrewder

In SourceTree, I'm getting the "fatal: Authentication failed for..." error when I try to Push/Pull from origin.

The Git terminal from SourceTree asks for my username/password and, when I enter it, it works correctly (I'm able to do a push/pull anyway). However, nothing I've tried will allow me to use the push/pull buttons in SourceTree. I've updated my Git username every place I've been able to see something that resembles a username, I've gone to Tools > Options > Authentication > [My Account] and set the password (which is a private access token).

I saw a similar question that mentioned "There is a SourceTree Application password stored in the login keychain." But I have no idea what the login keychain is or how I can fix it in SourceTree.

Details:

- SourceTree version 2.1.10.0

- Git version 2.7.0

- Windows 10 Pro, 64 bit

- origin server is Visual Studio Team Services

I'm not sure why it stopped working (I haven't changed my VSTS password and all my private access tokens are still valid), but I seem to recall an odd password box that popped up a week or so ago that I believe came from SourceTree. I might have entered the wrong password, but didn't see any problems at that time (I haven't pushed/pulled since then, so wouldn't have seen any problems until today).

What am I missing?

Accepted answers

bbrewder

David's answer to this question worked for me...

https://community.atlassian.com/t5/SourceTree-questions/How-to-update-HTTP-S-credentials-in-sourcetree/qaq-p/297564

The only thing that worked for me was navigating to C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree and removing the passwd file.

Once that file was deleted, I just did a "Push" and it finally asked for my password.

A note to Atlassian, there should be a much simpler way to do this than spending hours searching the Internet looking for an answer. If getting the Authentication page to work as expected is not possible, then perhaps just a button that users that are having trouble can press on the Authentication page that would reset all the passwords (basically just delete this file for us).

All comments

bbrewder

David's answer to this question worked for me...

https://community.atlassian.com/t5/SourceTree-questions/How-to-update-HTTP-S-credentials-in-sourcetree/qaq-p/297564

The only thing that worked for me was navigating to C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree and removing the passwd file.

Once that file was deleted, I just did a "Push" and it finally asked for my password.

Mariano Gomez Bidondo

Thanks a lot! I was speending 2 days touching options in the sourcetree. This answerd save my day!

Aiuursrage2k

yeah it worked for me as well. I cant believe that source tree would be so lazy, this is a software thats used by millions of devs.

Akul Bhatnagar

Awesome!!!

gmmaduro

JUST GO TO TERMINAL IN THE CORRECT FOLDER

TYPE: GIT PUSH

USERNAME AND PASSWORD

DONE!

euan brown_d8jh66

If you are using sourcetree with bitbucket, I had to go in and change the Username to an email address in the file location below. I believe bitbucket swapped the log in from using usernames to email addresses but source tree wouldn't take it on it's normal login pop up screen.

C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree\accounts.json

Eric Wolfe

Thanks for menting this, though I had to switch the Username back to our network user from the email address.

Alan Rasmussen

That was easy. Worked for me with Window 7. Thanks.

Advait Deshpande

I am putting all the steps I tried in the sequence and finally one thing worked. The solutions are suggested by other Stash/Sourcetree Users.

Solution A, Didn't work. Might work for others. Good Luck!

Make sure SourceTree is closed
Make sure the files are backed up in the following folders before removing the files
Remove files "bookmarks.xml", "opentabs.xml", "userhosts" in C:\Users\<username>\AppData\Local\Atlassian\SourceTree\
Remove file in C:\Users\<username>\AppData\Local\Atlassian\SourceTree.exe<random_string>\<version_number>\user.config
Open SourceTree again to test if it worked or not.

Solution B. Didn't work. Might work for others. Good Luck!

Navigating to C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree and removing the passwd file.

Solution C. Worked. Might be due to above steps performed above.

Sourcetree > Tools > Authentication > Deleted my Stash account > Added it again.

I hope the above post helps!

omaracrystal

I solved the issue by looking up Keychain Access with spotlight then deleted the Application password for that particular git url. I then opened the repository through SourceTree and it prompted me for a new password. The Keychain Access was then updated and worked after that

daniel_foster

Nothing is working for me. This is so frustrating, I have lost days messing about with this and two of my team are also having the same issue. Its not like I have an urgent build for 100,000 users that I need to get out the door or anything. I think its time to take my business elsewhere

Ales Svoboda

Thanks for summarization. Solution A worked for me.

Chris Schiebel

this was the only thing that worked for me on a mac, thank you!

Alan Wasem

ugh

unknown

Go to Tools -> Options in SourceTree and then go to the Authentication tab on the Options popup. Delete all of the stored passwords. Try again, you should have another opportunity to enter authentication credentials. I'm using 3.0.8 and that worked for me.

chaowangplaytech

I delete password file and it works, soure tree is terrible

Alan Wasem

On my Mac for the past 3 or 4 weeks I have had to reset my .ssh key once or twice a week. The way I do this is by searching for a folder in finder (shift + command + g) ~/.ssh/ and delete the bitbucket files .pub and all others. Then in sourcree accounts it reverts to another .ssh key I have in the folder. Hold option to change the button (where copy to clipboard usually is) to show generate new bit bucket key, with option held click that new button. It will ask for a pass phrase which can be whatever and will never ask for it again and then sometimes brings up another window where you’ll have to type your atlassian password. Once source tree has generated a new key the save option is still greyed out. You have to click the drop down menu for ssh or https and then either toggle it from https or just click ssh again and you’ll see the save button enable. At this point you can copy the new ssh key and add a new key on the bitbucket settings page. I hope this helps someone it’s crazy frustrating.

Anton_s6240l

Solution B works perfectly

Vincent Simonin

That did the job for me, thanks.

Narendra Kekane

Great it's work for me as well. My Source tree version was 3.0.12

Megan Moore_b754lr

This worked for me. I had just updated my DI2E (Bitbucket) password, and even though I tried updating the password with the edit button in SourceTree, that didn't work. Removing all the passwords worked. I am using 3.0.17.

imampriyanto

Yes, it absolutely helped me

Mandar Godse

Somebody at Atlassian needs to write a blog with clear steps to resolve this issue, this continues to be an issue for many people. I had originally reported my problem in 2017 and we are in 2019 and people still seem to be struggling with basic functionality such as login.

I run into these errors every time my password is changed. Recently I had to uninstall and reinstall the software to get authenticated. Is this really a solution ? I hope somebody at atlassian takes this seriously and write a clear documentation about this issue. When done please post the link to this issue.

unknown

B & C option works together

Linus Bårström

For anyone still having this issue, you can go in Repository>Refresh Remote Repository. This seem to re-enable the authentication form .

binla

Awesome!! it's work fined for me.

Hercules_0v6m74

So here we are in 2022, and these problem are still present!

Driving me NUTS.

I suddenly had authentication problems while contacting a remote git repository from Sourcetree, possible initiated by a password change on Windows.

Contacting over a web interface and from Visual Studio did WORK.
So I was sure of my credentials.

But trying all sorts things within Sourcetree did NOT change a damn thing.

Editing the credentials. Resulting in a bunch of saved passwords with different names. Why are there 2 right away with a single repository anyway?
Removing all of them. After which they SEEMED to be copied from the ones checked in Visual Studio. Yet still no success.
I was thinking of reinstalling an old version of Sourcetree, assuming some automatic update had messed things up. But I did not have other installation files.

Finally I found this post which saved my day, after hours of frustration.

I renamed the file C:\Users\USER\AppData\Local\Atlassian\SourceTree\passwd.

Then I asked my credentials and it all suddenly worked again, creating a new passwd file.

Come on Atlassian!

samsunoh22

The "fatal: Authentication failed" error in SourceTree typically occurs when there is an issue with the stored credentials or authentication settings.

samsunoh22

You can do the following things

Update SourceTree
Clear Stored Credentials
Check Git Configurations

Open a Git terminal from SourceTree and verify your Git configurations by running the following commands

git config --global user.name
git config --global user.email
git config -l

Take small steps and try these things, make sure to backup any local changes or repositories.

Martin Kužela

Great.

Removing the passwd file.

For 3 years I had to put username and password into URL as an workaround before finding this answer!!!