I have a Windows 8.1 PC at home that I occasionally use for work. Today at home when I attempt to pull from my project on Github I get the message
"fatal: unable to access 'https://github.com/GeokonRepository/....git/': SSL certificate problem: self signed certificate in certificate chain"
This worked in the last week or two from my home machine, and pulling worked on my work machine yesterday. Any help on how to diagnose what's going on would be appreciated.
I am having the same problem on two different computers while others in my office that are pulling from the same directory are not. I have uninstalled and reinstalled GIT and Tortoise GIT and the problem still exists. It was working fine on Monday. This is what is says when I try a pull:
git.exe pull -v --progress "origin"
fatal: unable to access 'https://github.com/gemsoftware/4pca.git/': SSL certificate problem: self signed certificate in certificate chain
git did not exit cleanly (exit code 1) (624 ms @ 5/17/2018 10:14:33 AM)
Any help would be greatly appreciated as I cannot continue work until this is resolved.
One interesting thing: if I simply open up my browser and directly access my Github project URL, it works just fine, and says the session is secure, even though Window git just said that there was a self-signed certificate in the chain.
I can access my account online as well, and it says it is secure. However, I still cannot do a pull either from EditPlus or by accessing the files directly on my machine.
Follow up - my machine at work is still able to pull. One difference is O/S, we run Windows 7 at work, Windows 8.1 on my home machine. At home I updated Git For Windows to the very latest version, but that didn't fix anything.
Both machines I am using run on Windows 7 and both were updated to the latest version of GIT (after the problem started). Others in this office are on Windows 7 as well and are not having a problem. I have an email in to the help desk, but I haven't heard anything yet.
I did hear from GitHub support:
This error is often caused by your network blocking the attempt by Windows to check the revocation status of a certificate, which then causes the whole operation to error. As this is affecting two Windows machines, with differing recent updates, it does sound likely that this is a network problem.
You can find a workaround for this issue in our GitHub Desktop repository here:
Can you give that a try and let me know how you get on?
I followed these instructions carefully, and I still have the problem. It shows that there is a very serious problem with GitHub on Windows that started a day or so ago. Evidently it is NOT my particular problem but a system-wide problem. It's tempting to think it's the result of the massive Windows 10 update but 1) my Windows 10 laptop showed the problem BEFORE it got the update and 2) some of the reports here involve older versions of Windows. I conclude that something very serious is wrong with GitHub.
Thank you so much for the information. I will send that workaround link to our IT guy. The problem is on two different computers in my office, but there is a third computer in this office that it is not affecting (they are all Windows 7). The two computers that are affected both have my login credientials and the third does not, so I'm not sure it is a network problem.
I am in the process of downloading a text editor and GIT to the Mac in our office to see if I can update the directory from there. Our IT guy logged in on his Mac with my credentials and had no problem. So, it seems it is a GIT/Windows problem that is not caused by the network or the update to Windows 10.
I will report back on Monday after we have tried the workaround and uploaded GIT to the Mac.
I tried the fix (downloading cacert.pem etc) but unfortunately that did not fix the problem.
Note that I'm having the problem at home, not in a corporate environment, so there aren't any issues with corporate policy etc.
At home I booted up an old Mac, installed the latest Git, and then was able to log into my github account and then able to start a git clone onto my Mac. So the problem isn't the network.