{"version":"2.1.307","anchor":"tls-env-handling-and-sandbox-proxy-message-changes","canonical_anchor":"tls-env-handling-and-sandbox-proxy-message-changes","heading":"TLS setting handling and a sandbox uninstall message reworked","tier":"internal","area":"Network","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/tls-env-handling-and-sandbox-proxy-message-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### TLS setting handling and a sandbox uninstall message reworked\n\n`NODE_TLS_REJECT_UNAUTHORIZED` is no longer named directly in two variable lists, and a message now says to run `claude sandbox uninstall` again\n\n**Unclear.** Whether `NODE_TLS_REJECT_UNAUTHORIZED` is still covered by the replacement list is not stated.\n\n**What**\n\n`NODE_TLS_REJECT_UNAUTHORIZED` controls whether Node.js checks the security certificates of the servers it connects to. It is no longer named directly in two of Claude Code's lists of environment variables (named settings passed to programs). Those lists now pull in the contents of another list instead.\n\nSeparately, a message that used to say a proxy was required now tells you to \"run claude sandbox uninstall again\", so the command to type is `claude sandbox uninstall`.\n\n**Why**\n\nThis may change which certificate-checking settings Claude Code passes along or removes. If you rely on `NODE_TLS_REJECT_UNAUTHORIZED`, check that it still behaves the way you expect.\n\n- Area: Network\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}