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

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?

9 answers

1 accepted

76 votes
Accepted answer

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). 

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

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.

Yeah its retarded

OMG thanks, It was driving me crazy

I resorted to git bash since source tree stopped working. Thanks for the fix. Sourcetree! \,,/

For some retarded reason the field to type in your email adress is greyed out and it has an email adress in it that doesn't even have an atlassian account. I can not change my email adress whatsoever. I've deleted the account file and restarted it. I've checked the tools bar into the authentication and removed everything there. I've even reinstalled source tree and it still won't let me change the email adress. Holy shit I regret updating to this horrible version. I'm stuck not being able to fetch or pull anything. Even the crash report pop up crashes when I submit this shit.

Like 1 person likes this

Fix: I removed everything from sourcetree and downloaded an older version. 

Removing the passwd file worked for me. This was driving me crazy for the past few weeks. Thanks for the solution! I was actually looking for other options to use instead of Sourcetree until finding this fix. It would really helpful if there were an easier way to force the password prompt.

Does anyone know what the password file is called?

thanks! This helped a lot.  It is a pity that such a simple thing is broken.  

It worked. Now I'm able to do all the operations in source tree tool. Thank you

Still working in 2018. Just solved my problem- next clone prompted for me to enter a password, and all went smoothly.

I updated the SourceTree and the authentications failed. I wiped out the SourceTree (uninstall and the directory deleted) and installed 2.4.7.0 SourceTree. I had the same problem: after asking the password to the local GIT server the session failed because of SSH_ASKPASS. I wiped out the SourceTree again and installed 2.1.2.5 version. It works normally.

SourceTree is a great tool if it works. The obvious recent modifications to the authentification code do not work.

It worked for me too. Stuff like this is why I down vote SourceTree when asked if I would recommend it. It actually prompts an email to my manager to go back to TFS.

Same here it worked for me after installing 2.1.2.5 Version. I hope atlassian is taking notes. GIT+SSH with username password does not work on 2.4.7.0. Please fix it.

I've reinstalled sourcetree and git (without credential manager and with it), generated several github acess tokens and without success.... and your solution helps! So THANK YOU ! I think that it should be in the docs or in the bug tracker :)

It seems that deleting (or perhaps renaming) a file worked for me as well. Thanks @Brian Brewder!

Of course, I had to find the path for MacOS.

For anyone else looking for that path it is ~/Library/Application Support/SourceTree and then look for a file similar to username\@STAuth-path.to.gitrepository.com

I simply appended the filename (just in case it didn't work). Afterward, I did a fetch (I'd imagine any server command would work) and I was prompted for a new password. 

Seriously?! a dev tool having such basic issue... I can't imagine amount of time lost by anyone using it including me

Thanks for the tips Brian

I had the same error and I saw this post, but deleting the password file did not work for me.  it turned out that my VSO personal access token was expired.  I had to renew it.  Just FYI for anybody who use visual studio online.

Thank you, this worked for me as well :-)

Thanks a million!

Thanks sooo much. i have looked for hours for this. 

Thank you so much... the tip still works today!

So before a fancy login box came up but my password never worked in it. But then when I detest this. The fancy login box didn't come up but a not so fancy box replaced it. The only difference is that my password worked on this one. So thanks for this :)

Thanks a lot! That was the problem!

Thanks a lot

Thank you!  This was exactly the answer I was looking for.

Just hit this same problem. Deleting the pwd file worked.

This bug needs fixing! How many thousands of dev hours are wasted on this stupid bug!

Thanks a lot. it worked seamlessly

Still working. Thx a lot

It's a pity, we have to do such things manually after a year...

Thanks a lot.
After 1 year this bug is still present and it almost led me to use gitkraken.
Please do better with sourcetree.

Still valid! Thank you so much! I was getting crazy! 

Thanks for the solution 
not so fancy box accept my pass :D

Thanks a lot !!! 

A week of research for this bug...

Deleting the password file of attlasian does the work !

I do not know what to expect to fix this bug, thank you very much!

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

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

JUST GO TO TERMINAL IN THE CORRECT FOLDER

TYPE: GIT PUSH

USERNAME AND PASSWORD 

DONE!

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

Like 1 person likes this

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

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!

  1. Make sure SourceTree is closed
  2. Make sure the files are backed up in the following folders before removing the files
  3. Remove files "bookmarks.xml", "opentabs.xml", "userhosts" in C:\Users\<username>\AppData\Local\Atlassian\SourceTree\
  4. Remove file in C:\Users\<username>\AppData\Local\Atlassian\SourceTree.exe<random_string>\<version_number>\user.config
  5. 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!

Thanks for summarization. Solution A worked for me.

Anton Salim I'm New Here Friday

Solution B works perfectly

1 vote

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.

That did the job for me, thanks.

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

0 votes

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

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

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Oct 23, 2018 in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

832 views 3 2
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