The build kept failing. Nobody knew why.
Logs were clean, credentials looked fine, and yet the application refused to talk to the outside world. After half a day of debugging, the answer was buried in a single, invisible line: an environment variable that pointed traffic through Zscaler.
Environment variables control more than secrets or database URLs. In networks protected by Zscaler, they can decide whether your code reaches the internet or times out forever. Miss one, and your pipeline stalls. Set the wrong one, and you might bypass required security or break access entirely.
The common setup includes variables like HTTP_PROXY, HTTPS_PROXY, and NO_PROXY. With Zscaler in the mix, these are often set to send traffic through secure inspection nodes. For local development, the settings might be different from production. That difference is where most problems hide.
Automated builds, containers, and CI/CD environments magnify the problem. A Dockerfile baked without the right proxy environment variable will fail in any network that routes through Zscaler. A CI job that doesn’t inherit the correct NO_PROXY entry for internal hosts will hang on requests that should never have left the private network in the first place.
To prevent surprises, document the required environment variables for every environment your code runs in. Keep them in version control as templates—never with actual secrets—and make it easy to inject them in your build and runtime. Check for differences between developer machines, staging, and production. Audit them after major network or Zscaler configuration changes.
When testing, make failures visible early. Capture and print the current environment variables in staging logs before starting any network calls. This simple step can save hours of silent debugging.
Getting environment variables right in a Zscaler-controlled network is not optional. It’s the difference between reliable deployment and endless guesswork. The fastest way to see a clean, working setup is to try it on a controlled platform. Spin up a live environment in minutes with hoop.dev and see every variable in action, end to end.