This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 586
Client unable to clone a repo after Azure DevOps Server upgrade #904
Comments
I am also facing similar issue. which I have reported on Stackoverflow |
Same exact thing here |
We have the same problem, but only if the user’s computer is not in the same domain as the Azure DevOps Server |
Are you trying to clone using an |
This was referenced Jul 18, 2020
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
If you're using Azure DevOps, can you access the repository in the browser via the same URL?
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.
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
The text was updated successfully, but these errors were encountered: