From 8f9bb6bccc65500a7d16078ffb3540407c2f90f6 Mon Sep 17 00:00:00 2001 From: Sehoon Shon Date: Wed, 7 Jan 2026 10:11:35 -0500 Subject: [PATCH] Update troubleshooting doc for UNABLE_TO_GET_ISSUER_CERT_LOCALLY (#16069) --- docs/troubleshooting.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 2daac9cd95..27a2679e9c 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -43,9 +43,15 @@ topics on: - **Cause:** You may be on a corporate network with a firewall that intercepts and inspects SSL/TLS traffic. This often requires a custom root CA certificate to be trusted by Node.js. - - **Solution:** Set the `NODE_EXTRA_CA_CERTS` environment variable to the - absolute path of your corporate root CA certificate file. - - Example: `export NODE_EXTRA_CA_CERTS=/path/to/your/corporate-ca.crt` + - **Solution:** First try setting `NODE_USE_SYSTEM_CA`; if that does not + resolve the issue, set `NODE_EXTRA_CA_CERTS`. + - Set the `NODE_USE_SYSTEM_CA=1` environment variable to tell Node.js to use + the operating system's native certificate store (where corporate + certificates are typically already installed). + - Example: `export NODE_USE_SYSTEM_CA=1` + - Set the `NODE_EXTRA_CA_CERTS` environment variable to the absolute path of + your corporate root CA certificate file. + - Example: `export NODE_EXTRA_CA_CERTS=/path/to/your/corporate-ca.crt` ## Common error messages and solutions