I've just upgraded to Visual Studio 16.11.5. When I do I get errors trying to connect to Azure devops. Azure shows the connection as successful but Visual Studio gives you a helpful message saying
"Failed to fetch from the remote repository".
It tells you to look in the output window, then the output window tells you to look in the output window :-)
NB This is different from similar stack overflow posts because this is specific to this release of Visual Studio. Prior releases did not have this issue. We've been able to verify this locally on a machine which worked before the upgrade and didn't after
CodePudding user response：
I can't comment on tonys answer since I'm lacking reputation. https://jessehouwing.net/configure-visual-studio-to-use-a-different-git-credential-manager-for-windows/ didn't help to solve this for me. I can confirm this issue and I'd like to give additional information in case it helps to solve this.
- I have a Gitlab instance running on my Synology. Everything worked until I updated to 16.11.5 since then the connection to Git is not working properly.
- Git with Rider works.
- Sync/Fetch doesn't work. I get the same redundant "Failed to fetch from the remote repository" in the output window. If I click Push or Pull this actually does Push/Pull from my Server. But it takes a while (1,2 minutes). In this case I get error messages in the output window that the Connection to the remote server could not be established because of an timeout. At the end of the message the IP-Address of my Server is mentioned in the format x.x.x.x:80. I guess Git tries to connect via http Port 80 but it should use Port 443 (https).
The original message in German is:
"Die Verbindung mit dem Remoteserver kann nicht hergestellt werden. Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat x.x.x.x:80"
CodePudding user response：
If you clear your authentication Manager setting then it appears to work again. Instructions here
but in case that link ever dies, find your .gitconfig file and just set
Manager =