Git authentication error: OpenSSL SSL_connect: Connection was reset in connection to dev.azure.com:443 #527
Comments
|
Hi @kerrpeter, please can you let me know what version of Git for Windows you are using by running It looks like you're running an older version of GCM Core (2.0.280). The latest version of GCM Core that is bundled with the latest Git for Windows is 2.0.567. You can get the latest Git for Windows from here: https://gitforwindows.org/ |
|
was, git version 2.29.2.windows.2 I just updated it, but same issue, works sometimes but not all the time C:<repro>>git --version git version 2.33.1.windows.1 C:<repro>>git pull fatal: unable to access 'https://dev.azure.com//': OpenSSL SSL_connect: Connection was reset in connection to dev.azure.com:443 C:<repro>>git pull Already up to date. C:\Xyea\LifePlan>git pull fatal: unable to access 'https://dev.azure.com//': OpenSSL SSL_connect: Connection was reset in connection to dev.azure.com:443 see above , didn't work, did work, and didn't again |
|
Thanks for updating and trying again. Hmm.. this is a strange error; a couple more questions for you:
|
|
Are you behind a proxy? No With trace on, when it works I get output below, but when it fails, I just get the error C:<repo>>git pull C:<repo>>git pull |
Ahaa! This is an interesting revelation! This means failure is happening in Git for Windows, and not GCM (GCM is not even being called when it fails). I also now read the error message more closely to see it is an OpenSSL error - GCM does not use OpenSSL on Windows, so this must be Git failing to make the network connection. I would recommend you open an issue in the Git for Windows repository: https://github.com/git-for-windows/git You would probably want to also include Git trace logs of the libcurl activity with @dscho do you have any other ideas? |
Hmm. That usually means network problems, but https://status.dev.azure.com/ currently shows everything should be all right. Sometimes it looks as if the Secure Channel backend does better than OpenSSL. Could you try running |
|
thanks, even with that, it sometimes works, sometimes doesn't, see several attempts below: C:<proj>>git -c http.sslBackend=schannel pull C:<proj>>git -c http.sslBackend=schannel pull C:<proj>>git -c http.sslBackend=schannel pull C:<proj>>git -c http.sslBackend=schannel pull C:<proj>>git -c http.sslBackend=schannel pull C:<proj>>git pull C:<proj>>git pull C:<proj>>git pull C:<proj>>git -c http.sslBackend=schannel pull C:<proj>>git -c http.sslBackend=schannel pull |
It could be a network problem on Azure's side. Or even in the routing specific to dev.azure.com. A connection reset (or a handshake that was never received) is a pretty clear indicator that already the initiating packets did not make it through. |
|
I am going to close this issue on GCM, since the problem is clearly affecting Git itself (not GCM). |
|
In our case it was an expired malwarebytes that was blocking the requests. Exactly as described above. Uninstalled it and worked like a charm again. |
|
yo estoy usando proxy para mi conexión de internet, como puedo subir mis archivos a git? por favor |
|
If you're facing this issue in Visual Studio: Open git settings and set the "Cryptographic network provider" to "OpenSSL" Here's an example |
|
I had the same issue, it turned out to be 'Killer Prioritization Engine" which is part of the drivers for the Intel wireless card. Turning this feature off in the 'Killer Intelligence Center' fixed the problem. |
Which version of GCM Core are you using?
Git Credential Manager version 2.0.280-beta+1f4c6db90f (Windows, .NET Framework 4.0.30319.42000)
Which Git host provider are you trying to connect to?
Azure DevOps
Can you access the remote repository directly in the browser using the remote URL?
Yes
[Azure DevOps only] What format is your remote URL?
https://dev.azure.com/`{org}`/...
[Azure DevOps only] If the account picker shows more than one identity as you authenticate, check that you selected the same one that has access on the web.
Expected behavior
I am authenticated and my Git operation completes successfully.
Actual behavior
It works sometimes, but usually takes 3 - 5 attempts, sometimes up to 10 attempts.
I get error "OpenSSL SSL_connect: Connection was reset in connection to dev.azure.com:443", but then it eventually works after several attempts with nothing else changing.
Sometimes it prompts for new credentials, but most of the time it doesn't
Logs
Set the environment variables
GCM_TRACE=1andGIT_TRACE=1and re-run your Git command. Review and redact any private information and attach the log.11:08:46.559413 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/bin
11:08:46.561432 git.c:444 trace: built-in: git pull
11:08:46.563403 run-command.c:663 trace: run_command: git fetch --update-head-ok
11:08:46.571381 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
11:08:46.573376 git.c:444 trace: built-in: git fetch --update-head-ok
11:08:46.577366 run-command.c:663 trace: run_command: GIT_DIR=.git git remote-https origin https://dev.azure.com/
11:08:46.585344 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
11:08:46.587339 git.c:729 trace: exec: git-remote-https origin https://dev.azure.com/
11:08:46.587339 run-command.c:663 trace: run_command: git-remote-https origin https://dev.azure.com/
11:08:46.596316 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
fatal: unable to access 'https://dev.azure.com//': OpenSSL SSL_connect: Connection was reset in connection to dev.azure.com:443
The text was updated successfully, but these errors were encountered: