The certificate — or the root at the top of its chain — was signed by nobody the client trusts. A lone self-signed certificate means the server was never given a real one; “self-signed certificate in certificate chain” usually means a private certificate authority, or a company proxy or security product inspecting HTTPS.
curl: (60) SSL certificate problem: self-signed certificate in certificate chain
How 5 other clients word the same error
Firefox
Error code: MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT — “The certificate is not trusted because it is self-signed.”
OpenSSL 1.1.1 and older
self signed certificate in certificate chain
Python
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1028)
Node.js
Error: self-signed certificate in certificate chain — code: SELF_SIGNED_CERT_IN_CHAIN (or DEPTH_ZERO_SELF_SIGNED_CERT)
Chrome, on a local network
NET::ERR_CERT_SELF_SIGNED_LOCAL_NETWORK
| Error | MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT |
| Usually fixed by | Either side |
| OpenSSL | self-signed certificate (18), self-signed certificate in certificate chain (19) |
| Spelling | “self signed” before OpenSSL 3.0, “self-signed” since |
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 self-signed certificate vouches for itself. That is fine for a test server or a router’s admin page, but no browser or tool can tell it from an impostor’s, so it is refused on the public web.
“In certificate chain” means the chain the server sent ends at a root the client does not trust. On a site open to the public that is rare; on a company laptop it is usually the network’s TLS inspection, whose root is installed in the system but not in the tool’s own trust store — Python, Node, Java and Git often keep their own.
Why it happens
- The server still uses the self-signed certificate the software generated at install.
- A certificate from a private or company certificate authority.
- A company proxy, firewall or security product inspecting HTTPS with its own root.
How to fix it
- For a public site, replace the certificate with one from a publicly trusted authority — Let’s Encrypt issues them free.
- For an internal service, add the private root to the trust store of each client that needs it — not to every visitor.
- Behind inspection, give each tool the company root: SSL_CERT_FILE or REQUESTS_CA_BUNDLE for Python, NODE_EXTRA_CA_CERTS for Node, keytool for Java, http.sslcainfo for Git.
See it for yourself
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null
Read the last “i:” (issuer) line: a company or security-product name there means your traffic is being inspected, not that the site is misconfigured.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- X509_STORE_CTX_get_error — docs.openssl.org
- Error codes on secure websites — support.mozilla.org
- Errors — Node.js v26.10.0 Documentation — nodejs.org
- Install certificate manually — developers.cloudflare.com