Skip to main content
Curator utilizes internet access to connect to Tableau Server as well as Curator’s web servers for updates. When configured without outbound internet access, Curator upgrades must be performed manually and Tableau Server must be accessible within the LAN. Often, IT teams prefer to route internet traffic first through a proxy. When configured to work through a proxy, Curator doesn’t send requests directly to the internet. Instead, it sends requests to the forward proxy, which in turn forwards the request. To configure a forward proxy, add the following variables to Curator’s .env file:
proxy_override=http://proxy.example.com:3128
no_proxy_override=localhost,127.0.0.1

HTTP_PROXY=http://proxy.example.com:3128
HTTPS_PROXY=http://proxy.example.com:3128
NO_PROXY=localhost,127.0.0.1

http_proxy=http://proxy.example.com:3128
https_proxy=http://proxy.example.com:3128
no_proxy=localhost,127.0.0.1
Replace proxy.example.com:3128 with the hostname and port of your organization’s forward proxy. Port 3128 is the default port for Squid-based proxies; adjust as required.
proxy_override and no_proxy_override are read by Curator’s own code and apply to all Curator processes, including web requests served through Apache and PHP CLI processes such as cron jobs. The standard HTTP_PROXY / http_proxy variables are read by bundled third-party tools such as Composer (used during upgrades). Both upper- and lowercase forms are required because different tools each read their own convention.

no_proxy_override / NO_PROXY / no_proxy Values

Common values include localhost and 127.0.0.1. Keep the same bypass list across all three variables so Curator’s own code and bundled tools behave consistently. If Tableau Server is on the same LAN as Curator, add its hostname so that traffic to Tableau is not routed through the proxy:
no_proxy_override=localhost,127.0.0.1,tableau.internal.example.com
NO_PROXY=localhost,127.0.0.1,tableau.internal.example.com
no_proxy=localhost,127.0.0.1,tableau.internal.example.com
Any other internal services that Curator needs to reach directly, such as an SSO or identity provider, should also be added to the bypass list.
Since Tableau Cloud is a remote SaaS service, its traffic should flow through the proxy rather than bypass it.