J Wyman

@ericblade the most likely root cause for you issue is that GitHub rolled out TLS 1.2 as a requirement today. The GCM was updated to meet the requirement as of...

> I think my problems were caused the the GitHub TLS 1.2 roll out. First I had this issue which was fixed by installing the latest git for windows. This...

@pauldendulk I agree and it's unfortunate. We (Microsoft) are working closely with GitHub at options to avoid sudden service interruptions like this one, in the future.

@anoopqai have you read this notice? https://github.com/Microsoft/Git-Credential-Manager-for-Windows#notice-experiencing-github-pushfetch-problems If not, please do. If that doesn't work for you, then we can dig in deeper.

> 15:18:42.903641 ...tionArguments.cs:430 trace: [SetProxy] failed to parse 'domain:port'. > 15:18:42.903641 ...tionArguments.cs:433 trace: [SetProxy] proxy cleared. This is the .NET Framework `System.Uri` giving me heartburn. Seriously becoming a non-fan of...

Notice `http.proxy = 'http://127.0.0.1:3128'.` vs `http.proxy = '127.0.0.1:3128'.`. What changed in your environment to cause the `http://` protocol to be removed from your proxy address?

@ignaciosolergarcia @chucklu the lack of a protocol in the URL would cause the GCM to fail to parse the string value and recognize it as a URI (NetFx `Uri` type...

> If the GCM was skipping the proxy configuration how is that it was working properly (all the normal operations worked normally). Is that even possible? I do not know....

Thanks for all your efforts. Please remember that the GCM comes free with the Git for Windows Chocolatey package, so a separate GCM package may be unnecessary.

Looks like v1.16.2, which is/was broken. Please upgrade to v1.16.3 or v1.17.2 for the fix.