Git ssl-unable-to-get-local-issuer-certificate The TLS layer found no trusted issuer to complete the server's certificate chain.
Reviewed for reference consistency: August 11, 2026
Code is Safe
SECUREGit has paused the operation to protect your code. No data has been lost or corrupted.
What To Know
Where Did It Fail?
Commands That Trigger This
Technical Background
The phrasing is literal: verification failed while looking for the issuer of one certificate in the presented chain. Either the server should have supplied it, or the local store should already know it — and neither held the answer.
The failure is configuration-shaped rather than content-shaped. Pointing http.sslCAInfo at a complete bundle, updating the distribution's CA package, or installing the inspection appliance's root restores verification. Disabling verification entirely removes the protection and is not an equivalent remedy.
Underlying Causes
Frequently Asked Questions
Browsers ship their own trust stores and can fetch missing intermediates on the fly; Git's library relies on the configured bundle and the server's chain alone.
Disabling verification removes the guarantee that the host is who it claims to be; the durable fix is completing the trust chain on either side.
Related Git States
Your computer's DNS could not find the IP address for the remote repository's domain name.
The underlying HTTP client (cURL) failed to complete the network request.
The certificate presented by the server was rejected because its issuer revoked it.
TLS verification of the remote host failed outright, naming the CA file and CRL file.