Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Impossible to Push after changing password to BitBucket account

simonericci
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 25, 2019

Since I changed password I have huge problems using Sourcetree.

When I try to push I get always this message:

Pushing to https://xxxx

remote: Too many invalid password attempts. Log in at https://id.atlassian.com/ to restore access.

fatal: unable to access 'xxxx': The requested URL returned error: 403

I log at the given url and nothing change.

I already changed password 3 times in the last 24 hours, and nothing changed.

1 answer

0 votes
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 25, 2019

Hi Simone,

Welcome to the Atlassian Community.

Have you tried removing the passwd file? On Windows it is under C:\Users\<username>\AppData\Local\Atlassian\SourceTree\, on Mac it should be under ~/Library/Application Support/SourceTree/ I believe.

simonericci
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 25, 2019

Hello Mikael

 

I am on macOs. I tried another password change, and then in console:

 

git remote show origin

and by now it's working...

I hope no other regression will happen, since it already happened many times to go back to login error ...

Is there something to fix/delete in the macOs keychain maybe?

Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 25, 2019

You could try and update the password in the entry in your keychain and see if that helps. On Windows I know that for some of my users we had to remove the username from the URL to get it to work (we use Bitbucket Server).

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events