Bitbucket repository started returning “remote: Too many invalid password attempts. Try logging in through the website.” (403) since yesterday
Since yesterday, bitbucket repository started returning this on any request:
remote: Too many invalid password attempts. Try logging in through the website. fatal: unable to access 'https://email@example.com/xxxxxxxxxx/xxxxxxxxxxx.git/': The requested URL returned error: 403
This happens on both the server (trying to git pull) and client (SourceTree on mac).
The user employed on both sides is the same, I can login to bitbucket and see no problems.
Both SourceTree and git on the server use different “App Password” generated in bitbucket.
I am the only person using this account daily.
I created a new App Password and tried with it just to get the same error.
What can I do to solve the case?
Update #1: Generating a new App Password does not work for both server and client. Re-adding a SourceTree account with Basic authentication does not help too. Bitbucket even does not allow to come to authentication, as it seems – the new App Passwords “Last Access” snows nothing.
Update #2: The accepted answer is indeed a solution. This is quite strange, but resetting the password of the main bitbucket user account works. But the sequence is as follows: reset bitbucket user password; create a new app password for both server and client (SourceTree); for mac, remove the record for bitbucket in KeyChain Access; only try to pull or push from SourceTree after removing the record or the account is locked immediately!
8 Solutions collect form web for “Bitbucket repository started returning “remote: Too many invalid password attempts. Try logging in through the website.” (403) since yesterday”
The reason for getting the above error is due to Atlassion account lock & not related with App passwords.
So I have reset my Atlassian account(as per Atlassian’s servicedesk suggession ) using below url
git fetch is working fine.
If you forgot your current password you can reset password by below url
Hope this help 🙂
Atlassian have just released a fix:
We just deployed the fix for the root issue causing this bug. If you
could please retry your actions, and let us know if you run in to any
We recommend that, you log out of Bitbucket Cloud and login once
again. Then please retry again.
We apologize for any delays, or outages this issue may have caused
you, and your teams. Please feel free to let us know if you have any
For the past few days some users may have experienced 503 or 403
errors related to authentication issues when using Git and Mercurial
over HTTPS on Bitbucket Cloud.
We have just deployed a fix to the platform for this issue. If you
could please navigate to “id.atlassian.com” in your browser, and make
sure you log out of any active sessions.
If you could then attempt to login to id.atlassian.com with your
email, and password – please make sure to NOT use the Google login
form, and instead use the basic email/password fields. You may be
asked to go through a captcha screen, or even reset your password if
Once you get logged in properly to id.atlassian.com, if you could
please try your GIT/Mercurial operations again, and let us know if you
are able to successfully authenticate.
Please let us know if you encounter any issues, or have any questions.
We would again like to thank you for your patience, and apologize for
any downtime these issues may have caused you or your team.
Thank you, The Bitbucket Cloud Team
Atlassian related. I went to bitbucket, logged out, logged back in and git started working. Did not need to change my password. Took less than a minute.
It seems that in my case the problem is with OAuth authentication. If I switch to Basic authentication, everything works fine.
For SourceTree, in Tools – Options – Authentication, delete the BitBucket account and then click Add to add again the credentials but with one minor change: In Authentication combobox select Basic. Enter your bitbucket username in Username field and press refresh password. You’ll be prompted to enter your account’s password but if till now you used Google account to login, set a new password here https://id.atlassian.com/manage/change-password
Now trying to find out what’s wrong with OAuth.
I changed the password and it works fine.. 🙂
I’ve just changed the bitbucket password and it worked like a charm!
This issue can be occurred while using multiple bitbucket accounts. For this case you can just go to “Repository settings” -> “Remotes” and specify your login in the remote path like this
The following helped me:
“For SourceTree, in Tools – Options – Authentication, delete the BitBucket account and then click Add to add again”.