Git pull / push - unable to access HTTPS, SSL rout

Question

I'm using Git (and GitHub) on a daily basis and everything has been working fine and all of a sudden, I can no longer communicate with my remote GitHub repository through my Git commands. When I try to "Git pull", it gives the following error:

fatal: unable to access 'https://github.com/snahrvar/eatibl.git/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

So, I tested across multiple repositories, and I get the same errors on my computer. I had someone else interact with those same repositories, and it works fine for them. Prior to this error, I did an "npm install sharp" on a project and that ended up failing, and I suspect this may have messed with some SSL setting, but that's a wild guess!

Any general thoughts or guidance would be much appreciated!

If it's helpful at all, here is my environment:

• Git version: 1.9.4.msysgit.2
• Windows version: Windows 8.1

Answer 1

Updating Git was not enough in my situation. After debugging for several hours, this was my fix:

C:\wamp64\www\maandlastenmanager> git config http.sslVersion
tslv1.0

C:\wamp64\www\maandlastenmanager> git config http.sslVersion tlsv1.2

C:\wamp64\www\maandlastenmanager> git config http.sslVersion
tslv1.2

Answer 2

The comment by @andw worked for me:

Update Git version 1.9.5 to 2.15.1 using these steps:

In sourceTree, go to menu Tools → Options → Git → Use Embedded Git.

Answer 3

Same for me with Git 1.9.5.msysgit.1 too. I tried to install https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases/tag/v1.14.0, but no change.

Actually, nothing happen after installation; maybe I'm doing something wrong? (That may not help for the initial question, but for other people, yes!)

Answer 4

While connecting to a remote repository to fetch, pull, push, etc., I had the same error:

fatal: unable to access 'https://github.com/repository.git/': error:1
407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

I just reinstalled Git 64-bit in place of 32-bit and that fixed the issue.

After installation, verify the Git path in environment variables. It should be:

C:\Program Files\Git\bin\git.exe

Answer 5

Yeah, I encountered the same issue on a pull request today and the solution was to simply update Git by downloading the latest (2.16.2) 64-bit version of Git for Windows. It was released 5 days ago, on 2018-02-20.

Answer 6

You're likely running into an incompatibility with GitHub's deprecation of weak SSL encryption protocols:

Weak cryptographic standards removal notice

The solution will vary, but for Windows you likely need to upgrade the Git credential manager to 1.14.0

https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases/tag/v1.14.0