Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to update HTTP(S) credentials in sourcetree

I'm using Stash, Sourcetree and Crowd. Crowd authenticates with our AD server. One of our users' AD passwords expired today and he went to do some work via sourcetree and it wouldn't let him communicate with stash properly

He set up the repo initially as HTTP when he first cloned it. It asked him for his username and password and he says he remembers clicking "Save/remember password"

Where can I have him reset/remove these credentials.

I've already worked around the issue by setting up SSH keys for this user, but I'm interested in what the fix would be. Presumably something via the command line, as I've been through every GUI screen I would think could have the setting in it.

24 answers

1 accepted

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


Once this file is removed, restart SourceTree and execute a fetch or something else that requires access to the repo in question. SourceTree will then prompt you for your password, rewriting the cached credentials.


I hope this helps. Shoutout to my buddy Nick for the assist.


If you're a macOS user, Auke states below that "you can find the password files per repo it in ~/Library/Application Support/SourceTree"

This saved my time. Thanks!

Like # people like this

This worked great.  I've been digging into this for over an hour!  Thanks.

Like Adam_Domjan likes this

This is also the only thing that worked for me.  Josh is lucky, i've spent about 5 hours on this between 2 different computer and creating new passwords!


This worked for me as well.

worked, thank you!!

Only this solved "Authentication failed for" error for me. Thanks!

Saved me too. Thank you!

Alternatively, if you're a mac user, you can find the password files per repo it in ~/Library/Application Support/SourceTree

Like # people like this

Auke ter Horst You saved me! Thank you so much! I'm also mac user.

Thank you David!!!

It worked for me. Thx a lot !

Thanks David Keck! This saved me much pain and agony. 

Cool, worked for me, thanks a lot !

Only way I could get access to my remote repo again. Thanks heaps!!

Thank you so much, it's helped :).

This worked! Thank you very much.

Thank you so much! That's the only thing works for me. I have been spending too long on this.

Thank you so much! That's working!

This worked for me too! Thanks.

This was the solution!!! Spent some time trying to fix this... Thanks!!!

I'm so happy to see that this helped! Auke, I'll update the main answer with your macOS findings.

Thank you. This worked for me.

This was the answer for me to delete the C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree\passwd file,  however, I also needed to change the username, and there was no way to do this through the sourcetree interface.


I found a file C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree\userhosts    which had the wrong username.  I changed it there and restarted and then it was able to push github repos to the correct username.

Like # people like this

thanks David. your solution worked for Authenticate error.


1) the failure ocurred on my SourceTree v2.3.x.x, when I updated my network Windows password.
2) When I ran ST v2.0.20.1 executable, no authentication error was encountered.
3) When I re-ran v2.3.x.x again, the authentication error resurfaced again.
4) Then, I came upon your solution and tried it, v2.3.x.x is working fine now. The original password file was dated ard 2 months ago, likely the last time it was changed before i upgraded to v2.3.x.x?

5) Before all these, i also tried the Tools-> Options -> Password change method.
It says authenticated after giving the correct password, but when I fetched my Repo, the authentication will fail. So apparently the passwd file in (4) could not be updated, which caused repo actions to fail?

Maybe it's a version bug?

Yep! That is the solution. Thank you very much David! 

Thanks, this is the right solution

Thanks David! This worked perfectly, only wish I had found your answer sooner!

Works for me. Credentials are not visible anywhere on the UI, not on the Tools->Options->Authentication tab, repository settings or Windows Credential Manager. Is there a JIRA ticket about this issue?

This worked!! :)

Nice, it worked, thank you!!

Finally. Thank you!

This worked for me with version

Thank you, and thanks to Mauricio Salazar for the userhosts info!

Thank you so much! This worked for me with version Windows 7 64bit

Worked for me on the Mac.

Thanks - this also worked for me - however as it's a central file - if you are using other accounts through SourceTree (e.g. BitBucket, GitHub) then you may want to just remove a single account line from the file rather than deleting the whole file.

Plus, as the User account used by SourceTree is also referenced in answers here - To specify a specific user account (which is not the default) I found that setting userid in the repo path (Settings > Remotes > Edit) e.g. http://myRepoUser@myrepo:3000/organisation/myrepo.git worked for an internal git server.  

This worked for me only after changing my Windows password again, as Sourcetree does not seem to accept passwords that begin with a special character such as '-'. Once I changed my password to begin with a letter then everything functioned as expected.

THanks maan..

thank you so much! only this helped me, too

Not working for tried many times to login to git in vsonline it was working just fine, but removed the keys from keychain, also reinstall and tried to clean up everything, when i type the credential it does not work and show the following on my mac:

fatal: Authentication failed for;


Even the credentials are correct

Works for me. Thanks much!

Worked like a charm! Thank you!

Great. Worked for me too. Thanks

Worked! Thanks!

Funcionou pra mim! Obrigado! Thanks from Brazil!

This worked for me. Thanks

also worked for me

Thank you, David.  This worked for me.

Worked also for me.
Close Sourcetree, delete the password file, open Sourcetree, random fetch => correct login.

Worked for me, lost about 1 day of my life trying to fix it. 

Was trying to fix this for about a week and this fixed it

Saved my life. Thanks man!!!

This solved my problem. Thanks.

Many Thanks! Worked a treat!

Almost the end of 2018 and this problem still persist. Deleting the passwd file was the only way to get around. 

Thanks alot !

Yup did the trick, the problem started when i changed my Atlassian password, after few days i opened source tree and i couldn't login with new password, it kept asking for password over and over again. 

Once removed the passwd file then it all worked! They should address this on the SoruceTree app.




Thanks boy you are a great boy.

This helped me save time, thanks David!

Atlassian should fix this annoying issue.

Like Shawn De Alejandro likes this

This really helped me getting resolved the same issue that wasted my time troubleshooting. 

Thank you very much!

Million Thanks! You are rock!! 

Like Jaque Nande likes this

Thank you so much :D

thanks it worked like charm

Thanks so much

It works for me, thank you so much.

There is now a menu item for it (see answer below):  Tools > Options > Authentication

This half-solved my problem after upgrading to the latest version on Windows (3.3.8). I actually deleted all SourceTree folders under AppData just to be sure. Then I revoked my OAuth access to SourceTree from my Bitbucket account (through the website). Still wasn't working. I couldn't get past the "Registration" screen during installation that connects to BitBucket. It just stays on that screen after logging in and nothing happens.

Finally, I downgraded to 3.2.6 (what I had previously) and poof, everything was working again. I had to revoke/refresh my OAuth but at least I could open and work in SourceTree again.

Thanks - it worked for me too

It also worked for me.

If I change the password through UI it works for some hours and then it fails again probably because the passwd file is not updated.

Why does sourcetree uses credentials from two sources(windows credentials and passwd file)?

Like BartmanDilaw likes this

Worked for me. Impressive that this is still an issue after years, using Sourcetree version 3.34.

This save my day !

I can't believe that Sourcetree still did not fix this bug. 

Thanks for this, it fixed my issue and saved me lots of time.

Thankyou soo much this had worked for me and has saved a lot of time :-)

Worked for me too! 

almost 2021 and it is still the best option. thanks!

Don't expect any good in 2020!

Great !!! Thank you very much !!! 

Best solution out there, definitely saved time!

I had a similar problem on Windows 10 when I wanted to use a new account on GitHub.  SourceTree was using cached credentials, and not displaying them on its internal dialogs, and I struggled to find a way to clear them.  I only worked out what was going on when I tried from Git Bash and had the same problem.  The credentials were definitely NOT on Tools -> Options -> Authentication.

The reason is SourceTree uses the Windows Credentials Store, so rather surprisingly you have to go to Control Panel.  Then Users and Accounts/Manage Your Credentials/Windows Credentials (it defaults to Web Credentials, which isn't what you want).  I had an entry for under 'Generic Credentials'.  

I deleted this from the credentials screen and then tried to push from SourceTree, which now asked me for the new credentials and performed the push using them.

I don't know how easy Microsoft have made it for third-parties to at least show these credentials on their screens, but I would think this would be a reasonable enhancement for SourceTree to make.

Same procedure should be followed on Windows 7 if just trying to change the password through Sourctree options fails.

Thx man, solve my problem.

Thank you Rich, it worked for me, i was look at all the places for a solution. I had even removed the credentials from Web Credentials page. I saw there were 3 different credentials for git which when removed worked for me.

This worked for me, thanks!

This worked for me, Thank you

Untitled.pngDeleted these two lines and it worked.

This is what I needed, thank you!

So frustrating though, trying to figure this out. I'd really like to see a wiki page about this...

This was really helpful! I spent a lot of time on this and you saved me even more, thank you!

Just had this happen to me too. I'm suspecting the root cause of this is when the Atlassian migration occurred from using login names to e-mail addresses. These can be used interchangeably on Atlassian, but is probably not accounted for in Sourcetree? I had two password files stored, associated with a username and an e-mail. Sourcetree was probably looking at the wrong one, and there's no transparency in the Sourcetree UI.

2021 And this was the only thing that worked for me. Thanks for this!

14 votes

If this is Windows, you do this in Tools > Options > Authentication, you can delete or update any passwords there.

On the Mac, you can do the same by starting Keychain Access and locating the password entries there.

I had exactly the same issue on a Mac and could solve it using this answer.

Had same issue on my mac, and solved it by changing credentials on Keychain Access. Thanks!

Thx man, solve my problem.

This doesn't work for me. When you hit delete, it will not do anything. When you hit edit, it will create a new entry with wrong information.

This STILL doesn't work, even in the latest builds. Authentication says all good but when you pull/push you get authentication failure. It obviously stores the repo pass in some convoluted system that doesn't work.

Thanks, it worked for me

Thank you ... this worked great !!

Doesn't work in Windows, all says "authentication ok", but then pull gives again authentication error. Only thing that helped was to go and delete that file

This worked great for me -- I just deleted my password, then it asked for it next time I accessed the remote and all was good.

When I just "edited" it, it didn't work. 

Thanks man! It worked for me

This worked for me, thanks!

Thanks a lot !

On SourceTree 2.7.6 you can easily reset your repo credentials, without having to mess manually with files, by following these steps:

  1. Open SourceTree preferences
  2. Go to the Advanced tab, to the far right
  3. Find the host name of your repo under "Default usernames for URLs which do not include one", on the bottom
  4. Press Edit, clear the username (leave it blank), and press OK
  5. Close preferences, do a Fetch on your repo, and enter the new credentials when prompted

I had to remove all the account information in here, have it prompt me for username/password (tried to clone empty repo from BBS in SourceTree), then I was able to connect enough to clone. What a pain!

This solved my problem!  Thank you!

Solved it for me on Mac. Thanks!

This is the real solution!!!

Mac user: In High Sierra I found the Auth file in 

~/Library/Application Support/SourceTree

File: <username>

I removed this file, restarted SourcTree and was prompted for the password in the push process.

Update DATE: Dec/13/2019

Recently I received an email from github:

You recently used a password to access an endpoint through the GitHub API. We will deprecate basic authentication using password to this endpoint soon. We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit:

This works for me. Thanks!

HI all,

If after deleting the password file, authentication credentiels ...

still dosen't work, try to use terminal from sourcetree and do a fetch you'll have a window asking to enter your credentiels. and it will be working fine :)

Simply worked. Thanks

That worked.  Thanks very much :-)

In search bar type Credential manager - Windows credentials - find and modify password.

It worked for me.

It didn't work for me however I changed the 'Auth Type' in the Accounts to Basic and then manually added my new password. :)Screenshot 2020-06-11 at 16.25.18.png

Yup.. That worked!!! Thank you. 

Deleting file did the trick.

If you're a macOS user, Auke states below that "you can find the password files per repo it in ~/Library/Application Support/SourceTree"


Also, if you have issues changing the user name, in mac delete:

hostusernamemap file 

In my case I had multiple copies of Keys along with the updated one. I resolved by removing the old credentials from Keychain .

This worked for me (Sourcetree v3.2xx on Windows 10):


Problem: Failure to Authenticate:

Reason (why probably): because initial registration was done using Google Auth APIs, therefore...


1. Click "Remote Tab > Edit Accounts

2. Click on your saved bitbucket account

3. Click "Edit" again

..under "Credentials"

4. click "Authentication" and select "OAuth"

refresh and you should be set ..hopefully

Maybe u guys can give this a try:

1. Goto Tools > Options

2. Click Authentication tab. There's sections(for me Accounts and Git Saved Passwords) for previously saved passwords.

3. Just click on the desired account. Details for the account will be shown with Edit and Delete buttons

4. Click Edit. It will prompt a window for you to put your password.


Thank you David!!!

I had to go to the C:\Users\<user>\AppData\Local\Atlassian\SourceTree directory and delete the cache folder and the passwd and userhosts files. Restart Source Tree, do a pull and it prompted me for the ID and PW.

You can also simply add your username in front of you repository address: e.g: git clone


You will then be prompted to put in your new password on your next pull or push. From there you will not be prompted for a password until you change it again.

Can anyone tell me what the password filename is

As per the accepted answer (assuming you are on Windows) C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree\passwd

@Xolela Masebeni  this might work for a single repository but not for the hosted repositories dialog

You don't have to blow away your whole password store.

In SourceTree navigate to the repository in question, click the Terminal button and type `git pull`. It will prompt you for the required credentials then you're good-to-go in the GUI as well.

That didn't work for me.

Just use Git Desktop. Tired of this bloody popup authentication modal!!!!!!!!!!!!!!!!!!!

I agree completely. I've recently switched to Git Desktop and love the simplicity and ease of it.

Like Dean likes this

Mac OSX 13.3.3, deleting password files doens't work for SourceTree 3.0.1 when trying to connect to Atlassian Bitbucket v5.11.1 self-hosted server. I managed to connect to Cloud BB and was only then able to get into the app's options otherwise it's completely useless. I still am unable to use it with the above BB server we're hosting so another broken cr*p from Atlassian.

This didn't worked for me. There is no password file under C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree\

This is always what I get:


hanks guys. It was helpful

Just for the sake of having complete use cases here... I had what I thought was the same problem. Turned out that our auth scheme had changed and we started logging in with just the username portion of our email addresses... so jrypkahauer instead of The real problem came when I added "" to the list of default usernames for our domain.

So effectively I had inadvertently made it impossible for myself to use the correct username on the domain where our git repositories all live.

It took me nearly 4 months of fighting this to figure out why ONLY SourceTree forced me to use an old, invalid username but would still prompt for the password if it was provided. Today I went panel by panel thru the entire Preferences UI and finally found this one.

The credentials for windows are managed in the Windows Credential Manager in the Control Panel.

Unless Git-Credential Manager is installed and ruins everything!

Like Silver Põld likes this

Respectfully I must disagree with Steve's answer: It doesn't work at least for me because in Authentication there's no saved credentials for and stash. I updated all my credentials for bitbucket and other vendors on the web, later i have to find out that i cannot log in to bitbucket in sourcetree, and there's no way for me to clear saved credentials. Except maybe wipe the local storage where sourcetree saves the preferences etc. but that can't the solution.

Edit: environment is windows.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events