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 with Curator, Apache configuration files can be used. On Windows, the curator.conf file is a great place for this configuration. On Linux, /var/www/html/.htaccess, or any of the httpd.conf files can also be utilized. The proxy_override environment variable points Curator to a specific proxy for web requests. If needed, no_proxy_override can be used to specify a route that should not use the proxy for traffic. 
SetEnv proxy_override "http://proxy:80"
SetEnv no_proxy_override "www.example.com"

​
no_proxy_override Values

Common values for no_proxy_override include localhost and 127.0.0.1. If Tableau Server is on the same LAN as Curator, add its hostname or IP address as well so that traffic to Tableau is not routed through the proxy. Multiple hosts can be specified as a comma-separated list: 
SetEnv no_proxy_override "localhost,127.0.0.1,tableau.internal.example.com"
Shell environment variables such as export http_proxy=... or export HTTPS_PROXY=... do not work for Curator. Curator reads proxy_override and no_proxy_override from the Apache environment set via SetEnv directives, not from shell environment variables. Always configure the proxy using the Apache SetEnv directives described above.