Skip to main content
Version: v2.5

HTTP Proxy Configuration

If you operate Rancher behind a proxy and you want to access services through the proxy (such as retrieving catalogs), you must provide Rancher information about your proxy. As Rancher is written in Go, it uses the common proxy environment variables as shown below.

Make sure NO_PROXY contains the network addresses, network address ranges and domains that should be excluded from using the proxy.

Environment variablePurpose
HTTP_PROXYProxy address to use when initiating HTTP connection(s)
HTTPS_PROXYProxy address to use when initiating HTTPS connection(s)
NO_PROXYNetwork address(es), network address range(s) and domains to exclude from using the proxy when initiating connection(s)

Note NO_PROXY must be in uppercase to use network range (CIDR) notation.

Docker Installation

Passing environment variables to the Rancher container can be done using -e KEY=VALUE or --env KEY=VALUE. Required values for NO_PROXY in a Docker Installation are:

  • localhost
  • cattle-system.svc
  • .svc
  • .cluster.local

The example below is based on a proxy server accessible at, and excluding usage the proxy when accessing network range and every hostname under the domain

docker run -d --restart=unless-stopped \
-p 80:80 -p 443:443 \
-e HTTP_PROXY="" \
-e NO_PROXY="localhost,,,,cattle-system.svc,,.svc,.cluster.local," \
--privileged \

As of Rancher v2.5, privileged access is required.