git SSL certificate- Invalid certificate chain while accessing

Question

I\'m fairly new to github and git, but I do have git setup on my Mac (using Mavericks) and have added a repo on github. I\'m using MAMP and working on a Drupal site, and when I

Answer 1

We had this error in one of our Git servers that was using a non self-signed certificate. We have been able to identify it and to fix it: it was caused by an intermediate certificate (GlobalSign G2 certificate) that was not registered in our reverse proxy in front of the Git server (we are using HTTPS until the reverse proxy).

This bug report helped us to identify the cause.

We are using nginx as reverse proxy. The official documentation give insights.

And this tutorial explains how to fix it.

Answer 2

if you use self generated ssl key, you can try this.

git config --global http.sslVerify false

Refer https://confluence.atlassian.com/display/FISHKB/Unable+to+clone+Git+repository+due+to+self+signed+certificate

Answer 3

I recently (Jul 2014) had a similar issue and found on OS X (10.9.4) that there was a "DigiCert High Assurance EV Root CA" certificate had expired (although I had another unexpired one as well).

1. Open Keychain Access
2. search Certificates for "DigiCert"
3. View menu > Show Expired Certificates

I found two certificates named "DigiCert High Assurance EV Root CA", one expiring Nov 2031 and the expired one at July 2014 (a few of days previously). Deleting the expired certificate resolved the issue for me.

Hope this helps.

Answer 4

Check your clock! In my case I was using HTTPS but my clock was wrong, I disabled SSL but eventually I realized the problem was the clock. Updating the clock and reenabling SSL did the trick:

git config --global http.sslVerify true

Answer 5

I got this error after having been able to clone lots of repos with no problem. The problem was that I had a typo in my repo url's domain (github.om instead of github.com). I'm sure this error is correct in some way but not the most helpful for this specific problem.

Answer 6

Wondering when this has changed or why it worked for others, but for me the solution was basically to use https instead of http:

git config --global https.sslVerify false