PaulDotNet

I wrote a small .net core tool that checks if there are no IPv4/IPv6 DNS issues that may result in timeouts, repeated password entries and long push or pull times....

If you really want to know then check that it is from Git credential manager process.

Having the same problem today. Calls to bitbucket just time out here. https://github.com/Microsoft/Git-Credential-Manager-for-Windows/blob/430bc00458c16dfbbd7635b70288502998a3eea0/Microsoft.Alm.Authentication/Src/Network.cs#L373 I tried the same call with curl and it worked fine. Had no problems for more than...

There must be something wrong at the system level. I notice this problem when computer resumes from hibernation. After restart everything is fine. Used to have the same problem with...

Edge has nothing to do with it. I only speculate that Edge had the same problem and it was somehow fixed. In GIT cred manager case HttpClient.GetAsync call just times...

Now I think that there are two problems. First is that unexplainable HttpClient.GetAsync issue. The second one is weird logic that interprets network problem the same way as failed credential...

I tried playing with timeouts but even 35 seconds did not help. Same query from browser replied in less than a second. With very high degree of certainty I believe...

There is a "show full output" checkbox on the push window in SourceTree. Chech it to see some output. Not much by default but your can always compile GCM in...

The root of the problem could be windows DNS. In my case using VPN most of the time adds IPv6 addresses for the bitbucket.org. Those addresses are unreachable and when...

Ssh may solve the problem. Fixes by GCM upgrades most of the time are just random coincidences.