SourceTree version 2.1.11.0 is unable to authenticate to bitbucket server after changing my Active Directory password.
So far I have tried solving the capthca, removing vault entry, accounts.Json file and passwd file but nothing seems to be working.
Following is from sourcetree.log file
ERROR [2017-09-08 14:15:30,127] [13] [SourceTree.ViewModel.CloneNewDialogViewModel+<CheckSource>d__197] [MoveNext] - Could not determine repository from: [server url], output was:
ERROR [2017-09-08 14:15:30,127] [13] [SourceTree.ViewModel.CloneNewDialogViewModel+<CheckSource>d__197] [MoveNext] - fatal: remote error: CAPTCHA required
Your Bitbucket account has been locked. To unlock it and log in again you must
solve a CAPTCHA. This is typically caused by too many attempts to login with an
incorrect password. The account lock prevents your SCM client from accessing
Bitbucket and its mirrors until it is solved, even if you enter your password
correctly.
If you are currently logged in to Bitbucket via a browser you may need to
logout and then log back in in order to solve the CAPTCHA.
Visit Bitbucket at [server Url] for more details.
ERROR [2017-09-08 14:18:48,844] [30] [SourceTree.Exceptions.RemoteHostException] [.ctor] - Insufficient authentication credentials
ERROR [2017-09-08 14:18:48,892] [1] [SourceTree.Exceptions.RemoteHostException] [.ctor] - Failed to check login for user [User Name]
Hi Tewodros, I'm assuming you're able to access Bitbucket Server normally, just not able to connect SourceTree.
SourceTree for Windows uses the Git Credential Manager (GCM) to store credentials, can you check in there to make sure there are no remnants from the old credentials?
Also I would try wiping SourceTree preferences and, if none of the above works, a clean install of SourceTree:
Let us know how it goes!
Regards,
Ana
I updated to the latest version of SourceTree version 2.3.1.0 which resolved the issue I was seeing last week. Hopefully, I won't see any issues in the future when changing my AD password.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Ana Retamal
It worked for us some days and it appeared again even after the above mentioned workaround. Our current version of Sourcetree is 3.0.15. Is there any way we can get rid of this issue permanently.
Regards,
Bhakti Prasad Panda
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.