v1.17.0 fails to authenticate with BitBucket

[garretwilson]

I'm stuck here. I can't push or pull from my company's repositories or my client's repositories.

Originally I was using the following versions:

• git version 2.18.0.windows.1
• Git Credential Manager for Windows version 1.16.2

Yesterday suddenly I was unable to authenticate with Bitbucket, even though everything was working fine the day before, and my configuration hasn't changed in months. (This is a continuation of the discussion on #665, but seems to be a different issue than what made me open that ticket originally.) I started getting the same old sequence:

fatal: HttpRequestException encountered.
An error occurred while sending the request.
fatal: HttpRequestException encountered.
An error occurred while sending the request.
Username for 'https://github.com':

As requested, I updated GCM for Windows. I'm now running:

• git version 2.18.0.windows.1
• Git Credential Manager for Windows version 1.17.0

I rebooted, but still cannot access Bitbucket. Now the GCM authentication window for Atlassian Bitbucket comes up, but it won't accept my username and password. After two attempts, it reverts to asking for my password on the command line.

[whoisj]

Should be resolved by #712, well as soon as it is merged, a build is ready, signed, released... 🤪

[chrisjpalmer]

Thanks guys. I too am experiencing something like this.

I can push to bitbucket BUT it never remembers my password and I got the 'fatal: HttpRequestException' errors as well.

[dampee]

Can't wait for the release

[garretwilson]

Can someone at least give an estimate on when to expect it? From @whoisj 's earlier comment, I thought it would have been the same day, since I assume that it's stopping all these huge corporations in their tracks that are using Bitbucket with HTTPS and need to get work done. Or am I somehow the only one of a few affected?

In case it helps others, I found a workaround: a coworker suggested I use Eclipse, which uses their own EGit (based on JGit, a complete Java rewrite of the Git client). If you're stuck I suppose you can just install the latest Eclipse just so you can get some work done.

[whoisj]

@garretwilson ETA is ASAP. Waiting on @Foda to confirm that things are indeed fixed as it rather difficult for (Microsoft) to perform exhaustive test validation against Bitbucket (Atlassian). Ideally, we'll see the green light today and I'll get a signed update out today (09 Aug 2018) or tomorrow (10 Aug 2018).

[whoisj]

v1.17.1 is available.

[garretwilson]

GCMW-1.17.1-preview.1.exe allows me to push and pull now. Thank you!!!

[chrisjpalmer]

YES! THANK YOU :) HAHAHAH FINALLY

[chrisjpalmer]

Typing in my password got so annoying hahaha,

[dampee]

I had the same issue. Tested the update. And everything works fine again.

[PierreRoudaut]

Thank you so much !

[Ghasan]

In case someone here like me using native Windows OpenSSH, the issue is because urls have changed. Please check this document: https://docs.microsoft.com/en-us/vsts/repos/git/use-ssh-keys-to-authenticate

Here is an excerpt:

Important

SSH URLs have changed. Old SSH URLs will continue to work through December 1, 2017. If you have already set up SSH, you will need to update your remote URLs:

Verify which remotes are using SSH by running git remote -v in your Git client.
Visit your repository on the web and select the Clone button in the upper right.
Select SSH and copy the new SSH URL.
In your Git client, run: git remote set-url <remote name, e.g. origin> <new SSH URL>. Alternatively, in Visual Studio, go to Repository Settings, and edit your remotes.

[JefferyHus]

finally it works :'(