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.
- SourceTree version 188.8.131.52
- 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?
David's answer to this question worked for me...
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).
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.
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.
I updated the SourceTree and the authentications failed. I wiped out the SourceTree (uninstall and the directory deleted) and installed 184.108.40.206 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 220.127.116.11 version. It works normally.
SourceTree is a great tool if it works. The obvious recent modifications to the authentification code do not work.
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.
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.
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 :)
If you have multiple accounts set up, it's not necessary to delete the whole passwd file.
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.
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.
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.
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.
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!
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!
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
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
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events