Can't communicate with Remote Repo due to SSL Issues, anyone familiar with this?

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 repo through my git commands. When I try to “Git pull” or “Git push”, it gives the following error:

fatal: unable to access ‘’: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

So, I tested across multiple repos, and I get the same errors on my computer. I had someone else interact with those same repos 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: git version 1.9.4.msysgit.2 Windows version: Windows 8.1

1 Like

Github disabled TLSv1 connections, so that’s probabbly why it won’t connect. If you upadate git to the latest version (2.16.2) it will probbably work again.

Yep. That solved it!

This post was moved to a different board that fits your topic of discussion a bit better, even though you’ve already got an answer :grinning:

As you’ll notice, your Topic is now in the “How to use Git and GitHub” board. No action is needed on your part; you can continue the conversation as normal here.

Updating git may solve the issue (not tested yet on my side, because I don’t encounter issue with my git client right now), but I can’t get files using curl or wget. They both encounter this same error…

I tried the --ssl... -1 switches and -1, -2 and -3 ones with curl, and --secure-protocol and --no-check-certificate.

Since I need to get programatically some releases from []( repos, what is the solution?

Adding --secure-protocol=TLSv1_2 to wget might help. If it errors about that not being a supported protocol type, then it means you need to update to wget version 1.16.1 or above.

@mymindstormAlready tested this option, and figured that the SSL support had to be updated on my side.

It’s done now, and all seem working.

Thankyou :slight_smile:

how did update ssl support. I am still facing same issue

this solved my problem too