Working via Proxy – Linux Endpoints
To establish a connection with a proxy server, the Action1 agent uses environment variables stored in /etc/environment file locally on your Linux endpoint. This file contains variable assignments that are applied system-wide at login.
To specify proxy settings for Action1 agent operation:
- On your target endpoint, open /etc/environment with a text editor (requires root privileges), for example, by running:
sudo nano /etc/environment
- Add the following proxy variables and specify their values:
http_proxy = http://<hostname>:<port> https_proxy = http://<hostname>:<port>
Consider the following:
- If your proxy requires authentication, add
<username>:<password>before<hostname>using@as a separator:http_proxy="http://username:[email protected]:8080" https_proxy="http://username:[email protected]:8080"
- Since some applications may use the UPPER CASE version of proxy rules, it is recommended to add it, too:
HTTP_PROXY = http://<hostname>:<port> HTTPS_PROXY= http://<hostname>:<port>
- Other environment variables set for your infrastructure can be preserved.
- If your proxy requires authentication, add
- Apply the changes. For that, you should restart the Action1 agent by running:
systemctl restart action1_agent
Changes will be applied system-wide. The systemd system manager will read the settings from /etc/environment and provide them to Action1 agent’s config. The agent will then use them to establish a connection to the proxy.
NOTE: The proxy rules are also utilized by other processes. Thus, you may need to specify additional settings that these processes require – like ftp_proxy or no_proxy (defines a list of hosts, domains, or IP addresses that should bypass the proxy, e.g., no_proxy=”localhost,127.0.0.1,::1,.localdomain.com”). For details about such specific settings, please refer to your app’s documentation.
See also: Working via Proxy – Windows Endpoints