View the original community article here
Last tested: Aug 17, 2020
In a nutshell: it's rare but possible. There isn’t a way in Looker to configure a proxy for Chromium, but at least three customers have found a way to configure Chromium itself to use the proxy.
The solution is to specify the proxy in the config file, like so:
- There is a config file at
/etc/chromium-browser/customizations/ - Set
--proxy-server var
( Or you could add below inside config file )
CHROMIUM_FLAGS="--proxy-server="Proxy IP:Port""
But wait! Chromium can be run locally and Chromium has to be run by the Looker user. Where/when/how would a proxy fit into this?
The proxy fits into this because if the dashboard is loading content outside of Looker, like an image added to a text file on a dashboard, the Looker server needs to be able to communicate out to the public internet. If the Looker server has a proxy configured for outbound connections from the Looker server to the outside world, then this would come into play.
When a render job is selected by the user or scheduled, Looker sends a request to Chromium and Chromium will load the dashboard/look in its entirety. Chromium loads from localhost:9999/dashboards.. in most situations, so a proxy blocking traffic to the outside world mostly isn't a problem. However, if the page tries to load things outside of Looker (such as Pendo stuff, Pinger sometimes is an issue, images on dashboards with links to the outside world, etc.), then those requests will be made from the Looker server as the Looker user in Chromium to the outside world, and potentially be blocked.
This content is subject to limited support.