Command Line and SDKs
First check whether the program uses the system proxy or needs an explicit HTTP or SOCKS proxy. Some runtimes read HTTP_PROXY, HTTPS_PROXY, or ALL_PROXY, but variable support, precedence, and where DNS is resolved depend on the tool. Don’t assume every SDK follows the same rules. Use the local address and port provided by your client rather than guessing from a tutorial.
Check whether NO_PROXY is unintentionally excluding the target service. After changing environment variables, restart the terminal or relevant process; running processes may not pick up the new values. For TLS certificate errors, check the system clock, certificate chain, and corporate network policies. Don’t hide the problem by disabling certificate verification.
IDEs, Extensions, and Remote Development
Cursor, GitHub Copilot, and other editor extensions may send requests through the app’s main process, extension host, or integrated terminal. If browser authorization succeeds but the editor still reports an error, check whether the authorization result returned to the app, then review the editor’s and extension’s own proxy settings. Access from the integrated terminal doesn’t mean every plugin uses the same route.
In remote development, containers, or subsystems, localhost refers to the current environment—not necessarily the device running the desktop client. First confirm the network boundary and a proxy endpoint that can be reached legitimately, then configure it according to the tool’s documentation. Exposing a local proxy to the public internet for remote access introduces additional risks and shouldn’t be the default approach.
CI and Automation
A CI runner’s network egress depends on its environment; local route settings aren’t uploaded with the repository. Check DNS and connectivity to the target API on the runner, and pass proxy settings to the process that runs the task. Self-hosted corporate runners may also need to comply with organization network policies. Egress changes on shared runners can affect regional availability checks.
Store API keys in CI secret variables, not in the repository, build artifacts, or debug logs. Keep troubleshooting logs to necessary error types, failure stages, and redacted request IDs; don’t expose authorization headers, full API keys, or subscription URLs. For long-running tasks, also plan for credential rotation, request cancellation, and server-side rate limits—not just the initial connection.