Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Why does new BitBucket login window fail?

lihram
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!
August 2, 2018

I have recently wiped my laptop clean, along with all the git credentials. Upon trying to work with my private git repository, I was prompted by the new bitbucket login. (See photo.)image.png

This does not accept my credentials.
I quickly figured out that I could simply press escape to use the legacy login method, but that one does not store the credentials, and thus I am stuck with having to do this every single time. (Sadly, this also means I am forced to use the command prompt, as tools such as SourceTree are not configured to default to the command prompt on closing this window.)

I am running Windows 10, using git version 2.18.0.windows.1.

 

Wondering if anyone has encountered this issue as well, and if so, how did you solve it?

 

Thanks in advance for your consideration and help.

1 answer

1 accepted

0 votes
Answer accepted
Ana Retamal
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 3, 2018

Hi Hilmar! 

Can you confirm you're using the right credentials to log in to your Bitbucket account (remember that Bitbucket uses the same credentials as you use for your Atlassian account at my.atlassian.com)? You can also try that by logging in directly

If Bitbucket is not accepting your credentials, have you tried resetting your password by clicking in Can't log in?

If you're still having issues after following those steps, can you send a screenshot of the error you get so we can continue helping you?

Kind regards!

Ana

lihram
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!
August 5, 2018

Hej Ana,

Thanks for your response!

I can confirm I am using the right credentials - the legacy login works fine, and I am also able to log into my atlassian account without issue. I tried resetting the password, and it made no difference.

UPDATE:

As I was reproducing the error, I cloned the repository again and it worked this time. The difference seemed to be the url of the remote repository as registered.

To clarify:

# old repository settings
> git remote get-url origin
https://bitbucket.org/<username>/<repository>/src/master/

This seemed to be causing problems with the new auth prompt, but worked fine with the legacy one.

# new repository settings
> git remote get-url origin
https://<username>@bitbucket.org/<username>/<repository>

Having stored the credentials, both pulling and pushing works fine with either setting, but the actual login only worked with the latter.

Thanks for your help!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events