Opens in a new tab

“unable to get local issuer certificate”: a missing intermediate, or an old CA bundle

The client could not find the intermediate certificate linking the site’s certificate to a trusted root. Usually the server is not sending it — browsers often patch that over, which is why the site “works in Chrome” but fails in curl, apps and scripts. Otherwise the client’s own list of trusted roots is missing or out of date.

curl: (60) SSL certificate problem: unable to get local issuer certificate
How 6 other clients word the same error

curl 8.17 and later (OpenSSL)

curl: (60) SSL certificate OpenSSL verify result: unable to get local issuer certificate (20)

Python

ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1028)

Node.js

Error: unable to verify the first certificate — code: UNABLE_TO_VERIFY_LEAF_SIGNATURE

Java

javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

PHP / WordPress

cURL error 60: SSL certificate problem: unable to get local issuer certificate

Git

fatal: unable to access 'https://example.com/repo.git/': SSL certificate problem: unable to get local issuer certificate
Errorunable to get local issuer certificate
Usually fixed byEither side
OpenSSLunable to get local issuer certificate (20), unable to verify the first certificate (21)
Why browsers may not show itChrome downloads missing intermediates; Firefox keeps a copy of all of them

Check the certificate a site serves

Enter the site’s domain: we connect the way a browser does and show the certificate, its chain and the TLS versions it offers.

What it means

A server should send its own certificate followed by the intermediate that signed it. Chrome downloads a missing intermediate from the address in the certificate, and Firefox ships every trusted intermediate in advance — so a server that forgets it can look fine in a browser. curl, Python, Node, Java, PHP and most apps do neither, and stop here.

If the server does send the full chain, the client’s own trust store is the problem: missing, or too old to contain the root — an old CA bundle, an outdated certifi, or Python on macOS without its certificates installed.

Why it happens

  • The server is configured with only the site certificate (cert.pem) instead of the full chain (fullchain.pem).
  • After renewal, the certificate was installed without the new intermediate.
  • The client’s CA bundle is missing or out of date.
  • A company proxy or antivirus substitutes its own certificates, which the tool does not trust.

How to fix it

  1. Run the check above, or openssl s_client -showcerts: if the server sends a single certificate, the chain is incomplete.
  2. Configure the full chain: nginx ssl_certificate pointing at fullchain.pem; Apache SSLCertificateFile with the chain included; on other servers, install the intermediate the certificate authority provides.
  3. If the chain is complete, update the client’s trust store: upgrade certifi for Python, point curl at a current bundle with –cacert, add a private root with NODE_EXTRA_CA_CERTS for Node or keytool for Java.

If you are visiting the site

  • Do not “fix” it with curl -k, verify=False or NODE_TLS_REJECT_UNAUTHORIZED=0: they switch off verification entirely, and curl, requests and Node all warn that this makes the connection open to interception.

See it for yourself

openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null

Lists the certificates the server actually sends — not a verified chain. One certificate (“0 s:CN=…”) means the intermediate is missing on the server.

Questions

Why does the site work in my browser but not in curl or my app?

Because browsers repair a missing intermediate — Chrome downloads it, Firefox has it already — and curl, Python, Node, Java and most apps do not. The fix is on the server: send the full chain.

Sources

Error text and meaning checked on 25 September 2026 against these official sources:

Hear about it before your visitors do

Add your domain and we check its certificate on every scan and email you before it expires, and when it changes or stops being valid — along with DNS, email and security headers. Free for your first domain.

Create a free account