What causes "GitHub Copilot Proxy and Certificate Errors"?

TLS-inspecting proxy such as Zscaler Root CA not trusted by the editor's Node runtime Copilot domains not allow-listed

How do I fix "GitHub Copilot Proxy and Certificate Errors"?

1. Test with curl: curl to the Copilot endpoint; if it only works with --insecure the certificate is the problem 2. Trust the corporate CA: VS Code: set http.proxy and the proxy CA settings, or set NODE_EXTRA_CA_CERTS to the root CA file JetBrains: add the CA under Settings > Tools > Server Certificates 3. Allow-list domains: Ask IT to allow the domains in GitHub's Copilot network docs 4. Last resort: http.proxyStrictSSL=false disables validation; use only temporarily

GitHub Copilot Proxy and Certificate Errors

Workaround available VS Code, JetBrains, Visual Studio Updated November 14, 2026Based on 3 user reportsHow we research

Quick answer

Corporate TLS inspection swaps certificates and Copilot rejects them. Point the editor at your corporate root CA instead of disabling checks.

Most likely fix: Test with curl

How to fix it

Try these in order — the most common fix is first.

1. Test with curl
1. curl to the Copilot endpoint; if it only works with --insecure the certificate is the problem
Did this fix it?
2. Trust the corporate CA
1. VS Code: set http.proxy and the proxy CA settings, or set NODE_EXTRA_CA_CERTS to the root CA file
2. JetBrains: add the CA under Settings > Tools > Server Certificates
Did this fix it?
3. Allow-list domains
1. Ask IT to allow the domains in GitHub's Copilot network docs
Did this fix it?
4. Last resort
1. http.proxyStrictSSL=false disables validation; use only temporarily
Did this fix it?