What
NODE_EXTRA_CA_CERTS is an environment variable, a setting you give a program from your shell. It points at a file of extra certificates to trust, which is common on company networks that inspect secure traffic.
- If the file cannot be loaded as one list, Claude Code now keeps the certificates it can load one by one and logs an error. Before, the whole file was either kept or ignored.
- A new warning covers a file that loaded only partly.
- A new warning covers a file with no readable certificate at all: "Claude Code ignored all of the NODE_EXTRA_CA_CERTS file: it holds no certificate that Claude Code can read." Certificates must be in PEM format.
- The warning about dropped self-named certificates (certificates that name themselves as their issuer) has been rewritten with detailed steps to fix the problem. It covers a renewed root certificate, explains that
NODE_EXTRA_CA_CERTSonly affects Claude Code's own connections, and names the escape hatchCLAUDE_CODE_DISABLE_SELF_NAMED_CERT_DROP=1, which keeps every such certificate whoever signed it. - The old version of that warning printed values that did not exist at that point, so it showed broken text. This is fixed.
Why
If you use a company certificate bundle, one bad entry no longer throws away the good ones, and connection failures now come with a message that tells you what is wrong and what to do.
Names in the bundleNODE_EXTRA_CA_CERTS
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Fixed every connection failing when the NODE_EXTRA_CA_CERTS file is empty, not PEM, or starts with a damaged certificate: readable…