fatal: unable to access 'https://…': SSL certificate problem: unable to get local issuer certificate
Git doesn’t trust the HTTPS server’s certificate — corporate proxy, self-hosted Git with an internal CA, or outdated CA bundle.
SSL certificate problemunable to accessserver certificate verification failed Meaning
Corporate SSL inspection re-signs HTTPS with a company root CA. Point Git at that CA instead of disabling verification.
Common causes
- Corporate proxy with its own CA
- Self-hosted GitLab/Gitea with a private CA
- Outdated Git for Windows CA bundle
⚡ Quick fix
- git config --global http.sslCAInfo /path/to/company-root.pem
- Windows: git config --global http.sslBackend schannel (uses the Windows store)
- Update Git
Detailed fix by platform
Git
git config --global http.sslBackend schannel # Windows
How to diagnose
- Network — Proxy/inspection?
- Server — Private CA?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Git
- rebase in progress fatal: It seems that there is already a rebase-merge directory, and I wonder if you are in the middle of another rebase.
- kex_exchange_identification kex_exchange_identification: Connection closed by remote host
- Repository not found remote: Repository not found. fatal: repository 'https://github.com/x/y.git/' not found
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 11 Oct 2026