CODEWITHSUNDEEP
gitbitbucketatlassian-sourcetree
sunsetjunks
sunsetjunks

Reputation: 740

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 protected]/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!

Upvotes: 56

Views: 32364

Answers (14)

ViajanDee
ViajanDee

Reputation: 684

HTTP could get quite buggy with bitbucket for some reason, I'd suggest you set up an SSH key with the following steps:

Set up SSH on macOS

Step 1. Set up your default identity

  1. From the terminal, enter ssh-keygen at the command line. The command prompts you for a file to save the key in:
$ ssh-keygen 
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/emmap1/.ssh/id_rsa):

  1. Press the Enter or Return key to accept the default location.

  2. Enter and re-enter a passphrase when prompted.

  3. List the contents of ~/.ssh to view the key files.

$ ls ~/.ssh
id_rsa  id_rsa.pub

The command displays two files, one for the public key (for example id_rsa.pub) and one for the private key (for example, id_rsa).

Step 2. Add the key to the ssh-agent

If you don't want to type your password each time you use the key, you'll need to add it to the ssh-agent.

  1. To start the agent, run the following:
$ eval `ssh-agent` 
Agent pid 9700
  1. Enter ssh-add followed by the path to the private key file:

$ ssh-add -K ~/.ssh/<private_key_file>

  1. So that your computer remembers your password each time it restarts, open (or create) the ~/.ssh/config file and add these lines to the file:
Host *
UseKeychain yes

Step 3. Add the public key to your Account settings

  1. From Bitbucket, choose Personal settings from your avatar in the lower left.

  2. Click SSH keys. If you've already added keys, you'll see them on this page.

  3. In your terminal window, copy the contents of your public key file. If you renamed the key, replace id_rsa.pub with the public key file name.

The following command copies the output to the clipboard:

$ pbcopy < ~/.ssh/id_rsa.pub

  1. Select and copy the key output in the clipboard. If you have problems with copy and paste, you can open the file directly with Notepad. Select the contents of the file (just avoid selecting the end-of-file characters).

  2. From Bitbucket, click Add key.

  3. Enter a Label for your new key, for example, Default public key.

  4. Paste the copied public key into the SSH Key field. You may see an email address on the last line when you paste. It doesn't matter whether or not you include the email address in the Key.

  5. Click Save. Bitbucket sends you an email to confirm the addition of the key.

  6. Return to the terminal window and verify your configuration and username by entering the following command:

$ ssh -T [email protected]

The command message tells you which of your Bitbucket accounts can log in with that key.

    conq: logged in as emmap1.
    You can use git or hg to connect to Bitbucket. Shell access is disabled.

If you get an error message with Permission denied (publickey), check the Troubleshoot SSH issues page for help.

Reference link: https://support.atlassian.com/bitbucket-cloud/docs/set-up-an-ssh-key/

Upvotes: 0

Egemen Hamut&#231;u
Egemen Hamut&#231;u

Reputation: 1712

Sourcetree Mac Developer stated in the link below that it is now fixed in 2.7.4 release, please update your Sourcetree in your Mac to this version.

https://community.atlassian.com/t5/Sourcetree-questions/How-to-solve-quot-Too-many-invalid-password-attempts-quot-error/qaq-p/609886#M21780

Upvotes: 0

Thilina Koggalage
Thilina Koggalage

Reputation: 1084

Delete the "passwd" file from,

C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree.

Then restart the SourceTree. Then fetch from the required repo. SourceTree will prompt a popup to enter the password of the repo. This worked for me.

Upvotes: 1

VladN
VladN

Reputation: 739

It seems that in my case the problem is 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.

Update

Another fix that seemed to work was deleting the passwd file from C:\Users\[your-user]\AppData\Local\Atlassian\SourceTree. Now in SourceTree do a git fetch/pull/push and you'll be prompted to login. Enter your credentials and everything should work fine now.

Upvotes: 8

Sagar
Sagar

Reputation: 21

Just re-enter your current password it will work fine.

Settings->Accounts->Edit

just login to your Atlassian account it must be resolved.

Upvotes: 2

passatgt
passatgt

Reputation: 4432

If you have Bitbucket open in your browser, sign out. After that, i was able to clone the repo i wanted with Sourcetree.

Upvotes: 2

Karthikeyan
Karthikeyan

Reputation: 748

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

https://id.atlassian.com/

So now git fetch is working fine.

If you forgot your current password you can reset password by below url

https://id.atlassian.com/login/resetpassword

Hope this help :)

Upvotes: 46

Mike Hughes
Mike Hughes

Reputation: 77

If you are using SourceTree and using oauth, i would suggest you go Tools > Options > Authentication and delete the saved passwords and your bitbucket account then add them back again. This worked for me. It will go off and refresh your token and add them back again.

Upvotes: 0

dj_serega
dj_serega

Reputation: 1

The following helped me:

"For SourceTree, in Tools - Options - Authentication, delete the BitBucket account and then click Add to add again".

Upvotes: 0

Igor Leonovich
Igor Leonovich

Reputation: 517

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 https://[email protected]/your-project/your-repo.git

Upvotes: 0

Viktor Nikitenko
Viktor Nikitenko

Reputation: 300

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.

Upvotes: 8

yoitsro
yoitsro

Reputation: 293

Atlassian have just released a fix:

Hi there,

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 further issues.

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 questions.

Thank you, Pravin

Update 2017-03-30:

Hi Everyone,

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 necessary.

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

Upvotes: 23

Antonio Gallo
Antonio Gallo

Reputation: 1

I've just changed the bitbucket password and it worked like a charm!

Upvotes: 0

Mesmerize86
Mesmerize86

Reputation: 673

I changed the password and it works fine.. :)

Upvotes: 1

Related Questions