Git - "SSL certificate issue: self signed certificate in certificate chain"

Question

I just started getting this error when trying to push my changes. I don't know what changed on my system and there should not be any self-signed certs in this connection.

Git has been uninstalled and re-installed. Git appears to be using the proper bundle: http.sslcainfo=C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt

Disabling cert checking is not an option.

How can I troubleshoot this issue?

The goal is to push my code to GitHub, but how did a self-signed cert get into this connection and how do I get it out?

Solution

I discovered that Kaspersky antivirus started using self-signed certificates in their "Web Anti-Virus" feature which caused Git to complain.

In order to work with the remote in any way over HTTP (push, fetch, pull, etc.) Kaspersky Web Anti-Virus needs to be disabled or that particular Git repo added to the exclusions list.

Comments

[SCote]

Key auth is a good work-around which completely slipped my mind. Thanks.

[VonC]

Good catch, more precise than my answer, +1.

[John Hanley]

Actually just click on their certificate using certmgr.msc (Windows) and restrict what the certificate can be used for so it does not mess with everything. Symantec does the same thing. Usually I just disable their certificates so that they cannot be used.

[gamliela]

Confirmed that disabling Kaspersky does help. But still I cannot add repo to exclusions list, this doesn't work. see forum.kaspersky.com/index.php?/topic/…