SourceTree Requiring CAPTCHA Login Every Time

[Justin Jacinto]

So every time I try to push or pull, the action fails and I get the following prompt:

git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks fetch origin
git: 'credential-osxkeychain' is not a git command. See 'git --help'.
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 https://ssbb.oiigds.com for more details.

I have found I am able to fix it by opening bitbucket in the web browser, logging out, logging back in, and completing the CAPTCHA check. Sometimes this check doesnt appear and I'll have to log out and in multiple times for it to work. 

If I just had to do this once it wouldn't be a problem, but its required every time I push or pull, even immediately after I've gone through the process. This never happened before, and no it happens every time. I've already tried updating SourceTree, and no fixes I've found online have worked.

Any ideas would be much appreciated.

Thanks,

Justin

[bgannin]

Hi Justin,

Our apologies for the hassle. A couple suggestions to try:

1. delete and re-add your Bitbucket account from Preferences/Options

2. if you are using SSH, verify the key is loaded by agent (ssh-add -l)

3. alternatively, switch from SSH to HTTPS and see if authentication calms down

Brian Ganninger
Senior Mac Developer, Sourcetree

[Justin Jacinto]

Brian,

Looks like deleting and re-adding  my Bitbucket account did the trick. I appreciate the quick response!

Thanks,

Justin

[Justin Jacinto]

Hey Brian, 

It looks like that fix worked temporarily for whatever reason, but I'm now experiencing the same issues again. I am using HTTPS.

Any other ideas I could try?

Thanks,

Justin