Client unable to clone a repo after Azure DevOps Server upgrade

[KeishaW]

Which Version of GCM are you using ?
From a command prompt, run git credential-manager version and paste the output.
1.20.0

Which service are you trying to connect to

• Azure DevOps
• Azure DevOps Server (TFS/on-prem)
• GitHub
• GitHub Enterprise
• Bitbucket
• Other? - please describe;

If you're using Azure DevOps, can you access the repository in the browser via the same URL?

• Yes
• No, I get a permission error.
• No, for a different reason:

If you're using Azure DevOps, and the account picker shows more than one identity as you authenticate, check that you selected the same one that has access on the web.

• I only see one identity.
• I checked each and none worked.

Expected behavior
I expect to be able to clone my repository using git clone [repo-url] without having to pass credentials in the [repo-url]

Actual behavior
TFS server upgraded to Azure DevOps Server 2019 (17.153.29522.3)
Attempting to clone returns fatal: Authentication failed for [repo-url]. No dialog shows for me to enter/update my credentials. I removed the credentials from Windows Credential Manager for git:[repo-server] hoping to get the dialog to re-enter my credentials, but this does not happen.

Set the env variables GCM_TRACE=1 and GIT_TRACE=1 and run your git command. Redact any private information and attach the log

09:15:29.150237 exec-cmd.c:236          trace: resolved executable dir: C:/Program Files/Git/mingw64/bin
09:15:29.150237 git.c:419               trace: built-in: git clone [repo-url] 
Cloning into '[FolderName]'...
09:15:29.183215 run-command.c:643       trace: run_command: git remote-http origin [repo-url] 
09:15:29.199773 exec-cmd.c:236          trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
09:15:29.201749 git.c:676               trace: exec: git-remote-http origin [repo-url] 
09:15:29.201749 run-command.c:643       trace: run_command: git-remote-http origin [repo-url] 
09:15:29.220876 exec-cmd.c:236          trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
09:15:29.403486 run-command.c:643       trace: run_command: 'git credential-manager get'
09:15:29.482979 exec-cmd.c:236          trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
09:15:29.484956 git.c:676               trace: exec: git-credential-manager get
09:15:29.484956 run-command.c:643       trace: run_command: git-credential-manager get
09:15:29.570235 ...\Common.cs:744       trace: [Main] git-credential-manager (v1.20.0) 'get'
09:15:29.660177 ...\Git\Where.cs:348    trace: [FindGitInstallations] found 1 Git installation(s).
09:15:29.667173 ...Configuration.cs:222 trace: [LoadGitConfiguration] git All config read, 15 entries.
09:15:29.743150 ...\Common.cs:85        trace: [CreateAuthentication] detecting authority type for '[repo-server]'.
09:15:29.765137 ...\Common.cs:224       trace: [CreateAuthentication] authority for '[repo-server]' is basic with NTLM=Auto.
09:15:29.767864 ...\Common.cs:765       trace: [QueryCredentials] querying 'Auto' for credentials.
09:15:30.148459 ...uthentication.cs:119 trace: [AcquireCredentials] '[repo-server]' supports NTLM, sending NTLM credentials instead
09:15:30.155493 ...\Common.cs:780       trace: [QueryCredentials] credentials found.
09:15:30.243348 run-command.c:643       trace: run_command: 'git credential-manager erase'
09:15:30.368281 exec-cmd.c:236          trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
09:15:30.373288 git.c:676               trace: exec: git-credential-manager erase
09:15:30.373288 run-command.c:643       trace: run_command: git-credential-manager erase
09:15:30.562283 ...\Common.cs:744       trace: [Main] git-credential-manager (v1.20.0) 'erase'
09:15:30.642961 ...\Git\Where.cs:348    trace: [FindGitInstallations] found 1 Git installation(s).
09:15:30.649936 ...Configuration.cs:222 trace: [LoadGitConfiguration] git All config read, 15 entries.
09:15:30.706925 ...\Common.cs:85        trace: [CreateAuthentication] detecting authority type for '[repo-server]'.
09:15:30.730890 ...\Common.cs:224       trace: [CreateAuthentication] authority for '[repo-server]' is basic with NTLM=Auto.
09:15:30.733887 ...\Common.cs:252       trace: [DeleteCredentials] deleting basic credentials for '[repo-server]'.
09:15:30.742881 ...aseSecureStore.cs:59 trace: [Delete] credentials not found for 'git:[repo-server]'.
09:15:30.770118 run-command.c:643       trace: run_command: 'git credential-manager erase'
09:15:30.817722 exec-cmd.c:236          trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
09:15:30.818723 git.c:676               trace: exec: git-credential-manager erase
09:15:30.818723 run-command.c:643       trace: run_command: git-credential-manager erase
09:15:30.899376 ...\Common.cs:744       trace: [Main] git-credential-manager (v1.20.0) 'erase'
09:15:30.978310 ...\Git\Where.cs:348    trace: [FindGitInstallations] found 1 Git installation(s).
09:15:30.985664 ...Configuration.cs:222 trace: [LoadGitConfiguration] git All config read, 15 entries.
09:15:31.051626 ...\Common.cs:85        trace: [CreateAuthentication] detecting authority type for '[repo-server]'.
09:15:31.074615 ...\Common.cs:224       trace: [CreateAuthentication] authority for '[repo-server]' is basic with NTLM=Auto.
09:15:31.078612 ...\Common.cs:252       trace: [DeleteCredentials] deleting basic credentials for '[repo-server]'.
09:15:31.086624 ...aseSecureStore.cs:59 trace: [Delete] credentials not found for 'git:[repo-server]'.
fatal: Authentication failed for '[repo-url]'

[btushar]

I am also facing similar issue. which I have reported on Stackoverflow

https://stackoverflow.com/questions/61981760/fatal-unable-to-access-getaddrinfo-thread-failed-to-start

[shad00m]

Same exact thing here
Never prompted for a password even on a fresh client and git fails with a authorization failed

[PArpagaus]

We have the same problem, but only if the user’s computer is not in the same domain as the Azure DevOps Server

[CrispyDrone]

Are you trying to clone using an https url? I was experiencing the exact same issue, when I change https to http, I am prompted to fill in my credentials.

[PArpagaus]

In fact, it works from the Command Line with http instead of https. Unfortunately, in Visual Studio there is still the same problem, the url of the remote repo is always https.