I figure out the problem that I was having. For some reason our network DNS shows both IPv4 and IPv6 addresses of Bitbucket. The IPv6 addresses are unreachable but Git Credential Manager which is used by Git which is used by Source Tree by default try to connect using IPv6 and just timeout. Further problem is made worse by faulty logic in Git Credential Manager which cannot distinguish between network timeout and invalid credentials. Thus network times out, Git Credential Manager thinks that credentials are wrong and asks again and again and again.
Web browsers can work around this problem by trying both IPv4 and IPv6 addresses. Git credential manager for some reason cannot do this so the only way to fix the problem is to either disable IPv6 or add IPv4 addresses of bitbucket.org and api.bitbucket.org to the hosts file.
@Ken Foskey, I deeply understand @Wayne Le-Trung. What is left to us besides the attack if issues with authentication are here for literally years and keep returning from different angles. For me it happens once a few months that I have to fight with it and try "a few solutions to this". Are we in XXI century or not?
Still not resolved. My sourcetree connects to Bitbucket, not Git Hub....and I am using SSH and I get the annoying REAUTHENTICATE pop up every 10 minutes. It's annoying and frustrating. How can they mess up something so basic and important? Are there any steps to follow? I don't want the "You have to do this" narrative...I want a step by step solution because I can't find anything and I have tried everything everybody has said here and nothing works.
I had the same. Very annoying. Finally I figured out it had something to do with my account being remembered twice. As myRepoSiteName.com and http://myRepoSiteName.com ->
remove the second one as short version will be added automatically. It helped in my case. Hope it works for you as well.
Yes - this solved, I had >1 account saved as well.
Add you BitBucket account, use the Oauth verify account - then ensure you only have one BitBucket account - set that one as default - close down SourceTree and start up again - finally the incessant prompt gone - +1 vote for this.
The best way to avoid this would be to use SSH but Stash should be able to store your password.
Go to Tools->Options->Authentication and make sure that your hostname, username, and password are all saved there.
Screen Shot 2015-05-04 at 1.33.55 PM.png
Alas, I tried everything I could think of including the above, wiping completely, reinstalling. Used SourceTree since before Atlassian acquired it. But I've had to switch away.
Any app that prompts the user for a password every few seconds should recommend how to fix the issue along the way.
Found the issue here: https://jira.atlassian.com/browse/SRCTREE-1747
marked as duplicate to this, but the permissions must be private: https://jira.atlassian.com/browse/SRCTREE-1746
Hope they fix it and we can use it again in the future. In the meantime there are lots of other clients.
Brendan, I has the same issue with the Authentication dialog constantly popping up. I managed to fix it by explicitly adding the username to all remote.url configurations.
Hope that helps.
Nothing worked for me until I dropped the sourcetree data and restarted:
1.) Take a screenshot of the sourcetree repo bookmarks so you will remember what they are
2.) Quit SourceTree
3.) Delete ~/Library/Application Support/SourceTree
(This removes all of sourcetree's internal data...bookmarks included)
4.) start SourceTree.
You have effectively Re-installed sourcetree now.
5.) click remote and you will prompted for your bitbucket credentials
You will need to add back your bookmarks but this is very easy (just drag and drop your project folders onto the source tree view after the restart).
None of the steps above worked for me. The underlying problem has to do with the store manager for Windows. Please follow this blog to update the credentials manager.
After following those steps make sure you set the latest version of the credentials manager.
git config --global credential.helper manager
As far as can make out this is caused by having multiple github logins. One thing that - does not resolve, but might work around it - is to remove any unused/old bookmarks (folders) - so if you open a new tab - you have a the list of repositories SourceTree has used. You can then remove unused ones (not from disk, jsut remove the bookmarks).
That workaround did it for me.
If you then need to work with one of the "old" folders again - you can of course just open this one (so potentially a workaround is to just open the current folder/project you're on in Sourcetree - and clear out your bookmarks).
Probably someone (might already be in the above) will have a command line script to clear all sourcetree bookmarks. ...
There's a number of answers already, but this particular process seems to have fixed it for me on Windows 10:
1. Uninstall SourceTree using Windows' "Add/Remove programs"
2. Navigate to C:/Users/<YOUR USERNAME>/AppData/Local/
a. Delete /Atlassian/
b. Delete /SourceTree/
3. Open Credential Manager and then Windows Credentials
a. Delete any reference to Atlassian or SourceTree
4. Reinstall SourceTree
5. In SourceTree open Tools -> Options
a. Click the Git tab
b. Click Update Embedded (if this fails you might need to close any Git/SSH processes including Pageant)
c. Click Embedded to use the Embedded Git version
I've been operating for awhile now without being prompted. Though I use SSH, not sure if this solves it for non-SSH use (or at all).
Remove all other authentications section in sourcetree other than git hub.
Then click Add or either go to Hosted repositories(to quickly check if it was successful) and click on edit accounts.
In credentials select OAuth and select refresh token. You will be redirected to bitbucket website and click on Grant access.
Now goto your fresh account in sourcetree and select Set as Default.
Done. Now you should see all your repositories in hosted repositories. It shows login error if it is not successful
I have had a problem that I have had to shut down sourcetree totally on mac (command Q) and restart in order to push. I could then successfully push my changes. Strangely I can always pull changes, only on push did it fail.
I am now experiencing an issue that I have to constantly connect using auth button to push. Lasts about 5 minutes and I have to connect again. I can still pull new changes.
Note I am on Mac. I am not being asked for my Mac Password, it is the actual auth to Bit Bucket that I have to sign on to, I am using google Auth. I did have github sign on as well. I removed this and my original bit bucket account then reinserted. No difference. Given it is mac password it is not issue 1947.
As noted elsewhere 1946 is private, cannot review for similarity.
I have noticed that this only happens on a client's bit bucket account. They have a lot of automation that signs on constantly and many users overnight. If I work at night I have issues, during the day it is much better.
It appears to be a licensing issue, not an application issue in my case. Check the licensing on your bit bucket account and ensure that it is sufficient.
I have never had an issue on my companies account.
That being said a better error message would make this more obvious to the user.
So I fixed this by switching to the system git rather than in built one. Thinking about it calmly: it is not the fact that authentication fails in the first place (though a better error message would also be good); it’s the fact that it spams the ui with dialogs. It needs some sort of error icon to show that there is an authentication failure and/or print in the log. One pop up dialog is fine. Constant dialog spam is just bad ui.
I suspect that behind the scenes the system is being constantly polled and eventually it builds sufficient errors that it stops. This counter is never cleared and when you try an actual operation it reports the error at that point.
It would be good if I could reduce polling on certain systems and also reset the counter so that the system correctly retries.
I have noted that switching system sign on on the user account and back again sometimes clears the issue. I do continue to experience this overnight on the client account. This is important once I clear issue during day it works fine for the day during the day time.
Overnight there are many more users on the client's account (Australian night time, European day time with many more Spanish programmers than Australian ones.). I can sign on and immediately have to sign on again overnight.
Jim Geppert's suggestion seems to work - or at least allow you to pinpoint at what point you start getting these prompts. Fon Win users:
This bug is extremely frustrating, and I was unable to solve even after:
This worked for me:
What's even worse is I have already uninstalled Sourcetree and wiped all traces of it I could find, partly because of this issue.
And guess what - 6 month after uninstalling, I STILL OCCASIONALLY GET THESE POPUPS!!!!!! Usually 3 on top of each other!!
For me on Mac, I tried many things suggested by other users, including deleting preferences files and Keychains, but what eventually worked for me was switching from the Embedded Git, to the System Git, in the SoureTree Preferences > Git.
It seems odd to me that this works, considering that they're both on the same Git version, but I verified it was really the fix by switching back to the Embedded Git again, and the problem came back, so I switched to System Git again, and haven't had a problem.
Announced in this blog, this holiday season we’re celebrating all things CI/CD and between now and the end of 2019 we’ll be showcasing content, use cases, feature announcements and more. One featur...
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