1

My Git installation refueses hard to git clone a repo due to a

fatal: unable to access 'https://X.X.X.X/svn/...': SSL certificate problem: unable to get local issuer certificate

error.

This is a common question around the Web, answered here and here. The solution consists of

1) either appending the certificate to the end of the cert-bundle file, or providing it as a solo file

2) making sure that the git config http.sslCAInfo property is pointed to the correct location in the correct config file.

On the account of finding which config file that is, here and here is where to look.

All configs listed in git config --list --show-origin point to the right cert-bundle, which of course contains the right key.

Any thoughts on what else can break the certificate validation process? The error message suggests that Git (or the lib doing the job) wasn't even able to get the certificate. Any thoughts on how's that even possible?

Community
  • 1
  • 1
hribayz
  • 139
  • 9

1 Answers1

0

When I want to interact with something that is going to use a self signed certificate, I just ask git to not care for it. It can be configured (I think) at the repo level (or even at the global level) but I'd rather do it on the commands like fetch so that I'm always aware of what's happening. git -c http.sslVerify=false fetch. That should do.

eftshift0
  • 26,375
  • 3
  • 36
  • 60
  • 1
    by extension ```git -c http.sslVerify=false clone blahblah``` – eftshift0 May 16 '17 at 13:35
  • Thanks @Edmundo, I'm aware of the possibility to disable SSL verification. Actually that's the workaround I'm currently using. I'd like to solve the issue though. It'd be nice to convince Git to accept that certificate and keep SSL on... – hribayz May 16 '17 at 13:42