Skip to main content

Proxy Settings

This document is a guide to enable customers to run the quickstart.sh scripts from behind a corporate proxy. These steps should be implemented prior to running any installations scripts.

Global Environment Variable Setup:​

The installation script must communicate with the Ziti Controller during the installation process to validate availability and also to enroll an edge router. Proxy settings should be disabled for the DNS address of the installation host, or the clientApi.advertisedHost setting for the Ziti controller.

Edit the /etc/environment file

http_proxy=http://dns-of-proxy:port
https_proxy=https://dns-of-proxy:port
no_proxy=localhost,127.0.0.0,::1,0.0.0.0,<DNS-OF-ZITI-CONTROLLER>

Changes to the /etc/environment file will only affect new process and terminal sessions. After applying these changes, log out and log back in and verify that the new settings are in place:

printenv | grep proxy
http_proxy=http://dns-of-proxy:port
https_proxy=https://dns-of-proxy:port
no_proxy=localhost,127.0.0.0,::1,0.0.0.0,<DNS-OF-ZITI-CONTROLLER>

K3s Proxy Configuration​

If installing using K3s, K3s will inherit proxy settings from the parent system. If for some reason k3s is not detecting the proxy settings properly, the following settings can be added by creating and/or updating /etc/systemd/system/k3s.service.env.

HTTP_PROXY=http://dns-of-proxy:port
HTTPS_PROXY=https://dns-of-proxy:port
NO_PROXY=127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,<DNS-OF-ZITI-CONTROLLER>

Restart K3s for the changes to take effect:

systemctl restart k3s

See the official k3s documentation for more information.