{"version":"2.1.275","anchor":"ca-cert-troubleshooting-message-now-lists-concrete-env-vars","canonical_anchor":"ca-cert-troubleshooting-message-now-lists-concrete-env-vars","heading":"CA-cert troubleshooting message now lists concrete env vars","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/ca-cert-troubleshooting-message-now-lists-concrete-env-vars","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### CA-cert troubleshooting message now lists concrete env vars\n\nSSL certificate error message now lists the specific env var to check per tool\n\n**What**\n\nThe TLS\/certificate troubleshooting message now names the specific flag or environment variable relevant to each tool that might be involved in a certificate error: `--cacert`, `SSL_CERT_FILE`, `NODE_EXTRA_CA_CERTS`, `REQUESTS_CA_BUNDLE`, `AWS_CA_BUNDLE`, `DENO_CERT`, `CARGO_HTTP_CAINFO`, `PIP_CERT`, `GIT_SSL_CAINFO`, `BUNDLE_SSL_CA_CERT`, `HEX_CACERTS_PATH`, and `NIX_SSL_CERT_FILE`.\n\n**Why**\n\nCertificate errors can originate from many different tools (curl, Node, Python, Deno, Rust's cargo, git, Ruby's bundler, Elixir's hex, or Nix), each with its own way of pointing to a trusted certificate. Listing the exact variable for each makes it much faster to find and fix the right one instead of guessing.\n\n- Area: Elsewhere\n- Names: `SSL_CERT_FILE`, `NODE_EXTRA_CA_CERTS`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}