Installing Enterprise Agents in Proxy Environments
Last updated
Last updated
Due to recent platform-wide naming, navigation, and URL changes in the product, you may notice some discrepancies between the product and the screenshots displayed in our technical documentation. The instructions and actual pages in the product are still valid and haven’t changed. Please bear with us as we update our screenshots to better match the in-product experience. See the full scope of changes on .
Some organizations' security policies require web communication (HTTP, HTTPS and FTP) from internal networks to the Internet be sent through a proxy server, in order to inspect and control the communication. Installation of an Enterprise Agent requires varying degrees of internet access, depending on the type of Enterprise Agent being installed. Additional or different installation steps may be required to install an Enterprise Agent when a proxy server is required for internet access.
Proxy servers have two principle characteristics which govern the way clients are configured:
Explicit or transparent Proxy servers which require each client to be configured with the proxy's IP address (or hostname) and port number, and (optionally) user credentials, are called explicit proxies. Proxies which do not require clients to be configured with proxy information are called transparent proxies.
SSL decrypting or non-SSL decrypting Proxy servers which perform SSL/TLS decryption require each client to be configured with the proxy's CA certificate (sometimes called a signing certificate or root certificate). Non-SSL decrypting proxies do not require clients to be configured with a CA certificate.
The figure below indicates the required configuration information for each of the four combinations of proxy type:
For proxies that are transparent and non-SSL decrypting, no additional configuration is required to perform the Enterprise Agent installation. Follow the installation instructions for your type of Enterprise Agent installation without a proxy.
The remaining three configurations of proxy are referred to in the remainder of this document with the following letters :
A: Explicit, SSL decrypting proxy configuration
B: Explicit, non-SSL decrypting proxy configuration
C: Transparent, SSL decrypting proxy configuration
Consult with your proxy or network administrator to determine which type of proxy you have, and obtain all required information before proceeding.
Deploying a Linux package agent
Deploying a Docker agent
Deploying an appliance
Deploying a Linux package Agent is performed by downloading and running the install_thousandeyes.sh shell script. The instructions for downloading and running the script are found by going to the + Add New Agent form of the Network & App Synthetics > Agent Settings > Enterprise Agents page, and selecting "Linux Package" for the Package Type, then clicking the Show Advanced Options link. The instructions are reproduced below:
In the first line, the curl command is used to download the install_thousandeyes.sh file. The curl command may require additional flags to use the proxy.
In the third line, the install_thousandeyes.sh script is executed. The script runs the Linux system's package management tool (if Ubuntu, the APT package manager; if Red Hat/CentOS/Oracle Linux, the YUM package manager) to download and install the Enterprise Agent software packages. To download and install the Agent through the proxy, the APT or YUM configuration file must be edited to include proxy information. Then the script configures the installed Agent. The script may require additional command line flags to use the proxy.
The following configuration steps may be required:
Install the proxy server's CA certificate
Configure the system package manager to use the proxy server
Run the curl command with modified flags
Run the install_thousandeyes.sh script with modified flags
For proxy configuration A, B, or C, use the following table of steps:
A
1, 2, 3, 4
B
2, 3, 4
C
IMPORTANT: Only install the CA certificate into the system CA certificate store. Do not perform the BrowserBot CA certificate installation, as the BrowserBot package is not yet installed.
The proxy used by the package manager need not be the same proxy used for the main Agent processes. Alternatively, if all needed repositories are mirrored on the internal network, or if communication to standard repositories on the Internet is permitted without a proxy, then this step can be skipped.
Modify the curl command to use flags for the proxy name or IP address and port number, and optionally a username and password:
Depending on the characters used in the username and password, the <USERNAME>:<PASSWORD> string may need to be enclosed in double-quotes to avoid being interpreted by the shell.
Run the chmod command to make the script executable. Then, with the proxy name or IP address and port number, and optionally a username and password, modify the script command's flags:
The script will install the Enterprise Agent and the optional BrowserBot component. Omit the -b flag if BrowserBot is not required. The script will also configure the /etc/te-agent.cfg file with the proxy information provided by the command's flags.
Alternatively, if the Enterprise Agent will use a PAC file to select its proxy, then modify the script command for the PAC file:
To see all the supported command line flags of the script, use the --help flag:
NOTE: Authentication to the proxy is performed via the HTTP Basic authentication mechanism, including CONNECT method requests for subsequent HTTPS-based requests. Basic authentication credentials are sent in clear text, encoded in Base64. Organizations which do not allow any credentials to be transmitted on a network in clear text should consider alternatives to credential-based authentication to the proxy, such as configuring the proxy to allow-list Enterprise Agents via their IP addresses.
Deploying a Docker Enterprise Agent is performed by running a series of docker commands on the Docker host. The commands are created by going to the + Add New Agent form of the Network and App Synthetics > Agent Settings > Enterprise Agents page, and selecting "Docker" for the Package Type, then filling out the form.
The following configuration steps may be required:
Install proxy server's CA certificate on the Docker host.
Configure Docker to use the proxy server.
Create Enterprise Agent Docker container with proxy configuration.
Mount proxy server's CA certificate in the Enterprise Agent container.
For proxy configuration A, B or C use the following table of steps:
A
1, 2, 3, 4
B
2, 3, 4
C
For other Linux distributions or non-Linux Docker hosts, consult your operating system documentation for more information on adding CA certificates to your system's certificate store, or contact the ThousandEyes Customer Engineering team.
IMPORTANT: Only install the CA certificate into the system CA certificate store. Do not perform the BrowserBot CA certificate installation.
This procedure configures the Docker commands to use the proxy server when communicating to servers on the internet.
2.1 Red Hat Enterprise Linux / CentOS / Rocky Linux / Oracle Linux
Create the /etc/systemd/system/docker.service.d directory:
Edit the file in which then Docker proxy configuration will be stored:
Enter the following environment variable configuration, replacing the sample values shown below with your proxy configuration information:
Reload the systemd configuration:
Restart the Docker service (warning, this command restarts all running Docker containers):
Verify whether the newly configured environment variables HTTP_PROXY and HTTPS_PROXY have the correct values:
Download the Docker image using the docker pull command:
2.2 Ubuntu
Edit the file in which the Docker proxy configuration will be stored:
Append the following content, replacing the sample values shown below with your proxy configuration information:
Restart the Docker service (NOTE: this command restarts all running Docker containers):
Download the Docker image using the docker pull command:
Log in to the ThousandEyes web application and open the Network & App Synthetics > Agent Settings > Enterprise Agents page. The commands to create the Enterprise Agent Docker container are produced by opening + Add New Agent form and selecting "Docker" for the Package Type, then by completing the form. An example of the completed form is below:
1, then
Depending on a customer's process for installing new systems, the proxy's CA certificate may not be installed by default. If the certificate is not pre-installed, the procedure to add a CA certificate to a Linux system with an Enterprise Agent is provided in the article . Select either the or the section.
The install_thousandeyes.sh script runs the system's package manager (APT or YUM) to download and install Agent packages. Additionally, the package manager will be used to automatically update the Agent packages and perform essential operating system updates. The procedure to configure the system package manager to use the proxy server is provided in the article . Select either the or section.
1, then , 4
Depending on a customer's process for installing new systems, a Docker host may not have the proxy's CA certificate installed by default. If the required certificate is not pre-installed, the procedure to add a CA certificate to a Linux system acting as the Docker host is provided in the article . Select either the or the section.
