BitBucket asked for password when pushing -- accidentally typed it wrong. Now what?

[Kush]

Hey guys,

I have been searching everywhere for this solution but basically. I clicked on Push and was met with this error message. I am pretty sure I put my password in the wrong way the first time. I am very new to this. The repo I am pushing to is a new repo on my Bitbucket. Any help is appreciated!

git --no-optional-locks -c color.branch=false -c color.diff=false -c color.status=false -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree push -v --tags --set-upstream origin refs/heads/develop:refs/heads/develop refs/heads/search-users:refs/heads/search-users refs/heads/user-authentication:refs/heads/user-authentication

Pushing to git@bitbucket.org:myname/mygitrepo.git

git@bitbucket.org: Permission denied (publickey).

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

and the repository exists.

Pushing to git@bitbucket.org:myname/mygitrepo.git

git@bitbucket.org: Permission denied (publickey).

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

and the repository exists.

Pushing to git@bitbucket.org:myname/mygitrepo.git

git@bitbucket.org: Permission denied (publickey).

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

and the repository exists.

Pushing to git@bitbucket.org:myname/mygitrepo.git

git@bitbucket.org: Permission denied (publickey).

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

and the repository exists.

Completed with errors, see above

[Daniel Eads · Accepted solution]

Hi Kush, welcome to the Atlassian Community!

From the looks of the output you've got, you're trying to use Sourcetree to commit to Bitbucket Cloud. There's a few ways to correct this issue:

1. You could configure Sourcetree to use SSH authentication instead of HTTPS authentication for your Bitbucket account. Instructions are available here - in short you upload your public key to Bitbucket and requests are signed using the private key on your computer.
2. You can try resetting the password in Sourcetree - some folks have luck by modifying the account details from the Accounts tab in the application's Preferences window. Depending on your account configuration, this may or may not work.
   
3. If you're not having luck changing the account preferences and don't want to use SSH, you can also remove the account settings file as described in this Community post. This will require you to re-enter credentials for all your accounts in Sourcetree, so tread lightly if you've got other accounts configured.

Finally if you are still seeing issues trying to connect to Bitbucket and the account is set to use Basic instead of OAuth access, you'll need to use an API token rather than a password to connect to your account (or change the account to use OAuth). We recently deprecated the use of passwords with basic authentication.

Cheers,
Daniel

[Kush]

Hey Daniel,

Thanks for the response. I am just now seeing it but it works now. I basically pushed and pulled my code until the error message went away. Percussive maintenance if you will. Sorry I don't have a definitive solution to this particular problem but if I do come across it -- I will make sure to document it for future use.

Thanks!