@shivanand217 which version of Git Credential Manager for Windows do you have installed?
This might be related to GitHub disabling weak cryptography. They did a test for 1 hour today, and they plan to disable them permanently on the 22nd.
https://githubengineering.com/crypto-removal-notice/
GCM is one of the known affected clients, and needs to be upgraded to v1.14.0
I met the same problem.
Using debug methods in issue #488
Problem: Unable to create TLS/SSL secure tunnel.
It turns out that this exception was caused by Git Credential Manager didn't support TLS1.2.
Version: 2.14.1.windows.1
@Elepover have you updated your Git for Windows and/or your GCM installations? I highly recommend just updating Git for Windows as it comes with the latest GCM anyways.
You are correct, the issue is caused by GitHub disabling support for weak encryption. GitHub's decision is a good move for the community, despite a day or so of anguish and frustration. Long-term the benefits of secure communication vastly outweigh the short-term problems.
If the issue continues even after you've updated your Git for Windows installation, please see this Developer Community issue for additional remedial actions you can take.
Most helpful comment
@shivanand217 which version of Git Credential Manager for Windows do you have installed?
This might be related to GitHub disabling weak cryptography. They did a test for 1 hour today, and they plan to disable them permanently on the 22nd.
https://githubengineering.com/crypto-removal-notice/
GCM is one of the known affected clients, and needs to be upgraded to v1.14.0