The ServicePointManager does not support proxies with the socks5 scheme #431
Comments
What is "socks5"? What is the actual HTTP/S end-point you're attempting to reach? The GCM is intended to support credentials for HTTP/S and SSH hosts. I've never even heard of "socks5". You'll need to provide more information - thanks. |
The proxy itself I'm using is not authenticated at all - on my network I have to access all services through a SOCKS5 proxy, which is supported by Git, however when accessing a remote with the credential manager enabled (said remote being GitHub, so it shows the GH authentication flow) this occurs - probably because .NET does not support SOCKS proxies by itself. To reproduce:
Noted is that the credential manager will give this error, then fallback to manual auth: entering the correct user/pass there will then work fine and use the SOCKS5 proxy for connecting to GitHub. |
For microsoft/whoisj: https://en.wikipedia.org/wiki/SOCKS nta, you can use polipo to convert your sock5 proxy to http/s, or you can use proxifier to force the proxy in any app externaly (but paid app). I know these are only workaround but it works. |
@nta I'd be more than happy to accept a contribution which adds socks5 support to the GCM. 😀 |
@whoisj @nta @tiliarou Hi , guys , when I do "git config --global http.proxy host:8888" then do a "git pull" (pulling from VSTS) in local Git Bash in Windows, I got this below error: Does it have something to do with the way I installed the Git-2.17.1.2-64-bit.exe ? Thanks, A |
Could be... I'm using standard git behind a proxy and it's working fine. I'm not using the microsoft git credential manager. Not sure this is the same issue of the OP here... |
Create an SSH key here: https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key
Looks like git does not support socks5 |
When trying to log in to a repository configured to use a SOCKS proxy (
http.proxy=socks5://127.0.0.1:12000
), the following error occurs, and git falls back to the basic authentication prompt:The text was updated successfully, but these errors were encountered: