Getting "SSL certificate problem: self signed certificate in certificate chain" on pull

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 ‘…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 ‘’: 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.

Thank you.

1 Like

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.  

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. 

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:—3326

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.

1 Like

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.

All updates en a my certificaten lte is een

My credentials work on a Mac as well which implys it is a Tortoise GIT problem.  

When I heard back from GIT, they said it could be a network problem and to be sure we have the latest versions of GIT and Tortoise GIT. 

They also said this: 

"You could also try switching from HTTPS to SSH:"

I know it is not a problem with our network because other users in our office are able to connect to pull from our directory with no problem.  We uninstalled and reinstalled GIT and Tortoise GIT to no avail.  We will try switching from HTTPS to SSH and see if that helps.  I will leave an update after that is done.

My IT guy was finally able to fix this for me.  He deleted my account and disassociated it with the company and then created a new account with a new user name and email address.  I reconnected to the company with the new account.  Next he updated my credentials within Windows and moved my directory to a different folder.  Then he cloned all of my repos.  I can now pull and commit without a problem.  I am sorry if this is a simplistic answer, but I don’t know all of the details.  I hope this helps! 

Hi @daveg-geokon@kparksgem@kimparks@zafarlte, and @brucesherwood,

Thanks for your patience. It’s clear that this is part of a bigger pattern which may have to do with a recent change in a Windows update. We’re discussing this problem internally and it would help us quite a bit if we could collaborate with you all to troubleshoot the issue further.

Since we need to do some deeper individual troubleshooting, would you mind submitting a help request in our help portal so that we can follow up with you and get some additional inforomation? You can point at this thread for background information and it would be helpful to know what version of Windows you’re using, what git client or clients you’ve encountered this problem with, and whether you’re operating on a personal network or a company network.


Suddenly, it works again! Thank you to whomever made this happen!

Bruce Sherwood

And suddenly my git pull is working again from home also.  It’s not clear why it failed or why it’s working now. 

I’ll try to summarize what I know:

  • I access the same Github repository from my home machine (Windows 8.1) and my work machine (Windows 7)
  • A few days ago only at home I started getting the “self-signed certificate” error trying to pull from Github
  • My work machine continued working just fine.
  • At home I was able to browse to my github repository (e.g. click on the same https link that I had tried to pull from).  That worked just fine.
  • At home I downloaded Git for Mac onto an old Mac and that worked fine yesterday (while my Windows machine was still failing).
  • Tried the fixes mentioned in this thread w/o any luck.

Not sure what this all adds up to.

Hi @daveg-geokon and @brucesherwood,

I’m so glad that it got resolved. If you have problems of this nature again, please feel free to contact GitHub Support directly, especially if these problems are impacting your ability to work. We try to provide the best support that we can through the Community Forum but using the contact form is the best way to get support for critical issues.


I also had same problem but installing Github again after securing my computer with different viruses it started working. It took some time but now its working. 

I just sent GitHub Support this message, alas:

When I try to push to my repository with SmartGit on Windows 10 I get this error message, which sounds very similar to the problem I had a week ago:

D:\0C\workspace\glowscript> git.exe push --porcelain --progress --recurse-submodules=check origin refs/heads/fix_displaying_PRIVATE:refs/heads/fix_displaying_PRIVATE
unable to access ‘’: SSL certificate problem: self signed certificate in certificate chain

I also tried cloning with GitHub Desktop and I get this:

Cloning into ‘D:\0C\workspace\glowscript2’…
fatal: unable to access ‘’: SSL certificate problem: self signed certificate in certificate chain


I was able to pull again last week after my IT deleted and recreated a new GIT account, then cloned all of my files and moved them to a different directory.  This worked well for a few days last week.  However, when I came in this morning after the long weekend… it is back to saying: 

“SSL certificate problem: self signed certificate in certificate chain”

git did not exit cleanly (exit code 1) (578 ms @ 5/29/2018 10:12:11 AM)

No one accessed my account or my computers over the weekend.  I am getting so frustrated, I am not able to do any work and the IT does not know where to go from here.  I cannot keep creating new accounts every week.