Run git config -list to get a list of all the Git configuration on the system, and check whether the proxy server is in use.

Solution: Configure Git to use the proxy server This issue also occurs when the connection can't establish through the proxy server, and you see the errors similar to 'unable to access :' or 'couldn't resolve host '. If you're using a proxy server but the Git configuration isn't set to connect through the proxy server, you might see the 407 or 502 error messages. Cause 1: Git can't connect through the proxy server To learn more about Git environment variables, see Git Internals - Environment Variables.

The level of tracing set for these variables provides more information similar to the following example about the errors that cause issue: Set the following variables in sequence, and run the Git commands for each set variable to get more information on the errors. To identify the cause of the issues, follow these steps:Įnable verbose tracing to set the verbose level of tracing for the Git commands that you're running. When you try to clone or push a repository in GitHub, some issues with proxy configuration, SSL certificate, or credential cache might cause the Git clone operation to fail. This article discusses problems that might occur when you try to perform Git clone or Git push function to an Azure DevOps repository.Īpplies to: Azure DevOps Services, Azure DevOps Server Issues while performing Git clone or Git push to the Azure DevOps repositories

Git credential manager