Proxy Configuration

NOTE - InsightOps and Proxy Support

InsightOps does not currently support the agent-based proxy configuration procedure detailed here. As an alternative, InsightOps does support a logging.json proxy definition with additional key-value pairs. See the InsightOps - Configure the Insight Agent to Send Logs page for instructions.

You can specify a Collector as your proxy

If you’ve already deployed one or more Collectors in your environment, you can target one of them to use as a proxy for this use case. The Insight Agent’s collection tasks do not distinguish between a Collector or another proxy type. Specifying either achieves the same goal of reaching the internet.

The proxy-port must be set to 8037 in accordance with Collector requirements.

Insight Agent versions 2.3 and later are proxy-aware and comply with proxy routing definitions for the purpose of communicating with the Insight platform at and its various subdomains. The agent follows the highest priority proxy definition found, whether configured at the operating system level or in the file structure of the agent, according to an obedience hierarchy.


The Insight Agent can only communicate through proxies that meet the following protocol requirements and authentication schemes.

Supported HTTPS Proxies

Your proxy must support the Request For Comments (RFC) 2817 standard, which specifies the HTTP CONNECT verb.

Authentication Schemes

Currently, only BASIC authentication is supported.

Agent Behavior With Proxies

If an HTTPS proxy is detected, the Insight Agent adds it as an additional communication route. Existing routes to any deployed Collectors or standard direct communication routes to the Insight platform are not removed in the process. Although the agent automatically determines the most efficient route through a calculated efficiency metric, proxy routes are always used if they can reach the Insight platform at the time of transmission.


Higher priority proxy definitions will override lower priority definitions.


Proxy Definition Source


proxy.config file - manual configuration applied to the Insight Agent installation directory


HTTPS_PROXY environment variable


Operating system configuration - "Internet Options" and WinHTTP for Windows.

"Network Settings" for Mac

Priority 1: proxy.config File

You can automatically configure the proxy.config file during a command line installation of the Insight Agent or manually after the agent has been installed.


The command line argument method works with both the certificate package installer and the token installer.

To configure the proxy.config file at install time with the command line:

  1. Download the Insight Agent installer for the operating system of your choice.
  2. Open a command line interface or terminal.
  3. Run one of the following installation or post-installation commands according to your endpoint operating system and include the proxy argument as shown ( appears here as an example IP address and port combination):
    • Windows - msiexec /i agentInstaller-x86_64.msi HTTPSPROXY=
    • Linux - sudo ./ --https-proxy=
    • Mac - sudo ./ --https-proxy=

If you want to configure proxy.config during a token-based agent installation, makes sure your install command also contains the following token and region attributes. Substitute <regionalID> and <UUID> with your corresponding region code and unique token:

  • Windows - msiexec /i agentInstaller-x86_64.msi CUSTOMTOKEN=<regionalID>:<UUID> HTTPSPROXY=
  • Linux - sudo ./ --token <regionalID>:<UUID> --https-proxy=
  • Mac - sudo ./ --token <regionalID>:<UUID> --https-proxy=

Alternatively, you can configure proxy awareness on individual agents that you have already installed by manually creating the proxy.config file in the agent installation directory.

To manually create and configure the proxy.config file:

  1. Browse to the following folder in your agent installation directory according to your operating system:
    • Linux - /opt/rapid7/ir_agent/components/bootstrap/common/
    • Windows - C:\Program Files\Rapid7\Insight Agent\components\bootstrap\common\
    • Mac - /opt/rapid7/ir_agent/components/bootstrap/common/
  2. Create a new file named proxy.config.
    • .config is the necessary file extension.
  3. Open proxy.config in a text editor and define your proxy address according to this example syntax:
{ "https": "" }

This JSON string stipulates that the agent must tunnel all HTTPS traffic to the address and port that you specify.

If you want to specify your proxy address with basic authentication, you can do so by modifying the proxy declaration string to include a username and password. Substitute <username> and <password> with the appropriate values according to this example:

{ "https": "<username>:<password>@" }

Priority 2: Environment Variable

While lower in priority than the manual proxy.config file configuration method, the agent regards the HTTPS_PROXY environment variable as the highest priority system-level proxy definition. Additionally, the agent also obeys any destinations excluded by the NO_PROXY environment variable.

NOTE - This method is intended for Linux assets

Configuring the HTTPS_PROXY environment variable is not necessary for Windows or Mac assets, nor do we recommend it given its constraints and procedural complexity. If you need to configure proxy rules at the system level for these operating systems, follow the instructions detailed in the Priority 3: Operating System Configuration section of this article.

However, the HTTPS_PROXY environment variable is the only system-level proxy definition source available on Linux assets. If you need to configure proxy rules at the system level for a Linux host, you must set the HTTPS_PROXY environment variable according to the instructions detailed in this section.

Linux HTTPS_PROXY Environment Variable Procedure

The HTTPS_PROXY environment variable must be configured in the Insight Agent service file in order to save properly and persist as the host is powered on and off. The agent service file is located in /etc/systemd/system/ir_agent.service.

To set the HTTPS_PROXY environment variable using the agent service file on a Linux host:

  1. Open a terminal on the Linux host.
  2. Navigate to your ir_agent.service file and open it with a text editor, such as vi:
vi /etc/systemd/system/ir_agent.service
  1. The output displays a series of categorical tags with variables under each tag. Under the [Service] tag, add the following line as shown and specify your desired IP address and port ( appears here as an example IP address and port combination):
  1. Save and close your changes.
  2. To finish, reload systemctl and restart the agent service:
systemctl daemon-reload
service ir_agent restart

Priority 3: Operating System Configuration

If higher priority proxy definitions do not exist, the agent obeys proxy rules defined by the standard proxy configuration tools featured by the Windows and Mac operating systems.


The agent supports both the Automatically detect settings and Use automatic configuration script options shown in the following "Local Area Network (LAN) Settings" window.

You can manually configure proxy definitions in the "Proxy Settings" window:

  1. Browse to the "Internet Properties" window.
  2. Click LAN settings.
  3. On the "Local Area Network (LAN) Settings" window, check the box under "Proxy server" to enable the proxy configuration fields.
  4. Click Advanced.
  5. Specify your proxy address in the "Secure" field.
  6. Specify any exceptions as necessary.


Since Insight Agent runs as the SYSTEM user, the following registry value must be used when using any of the above settings:

HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings

Additionally, the agent references WinHTTP settings if no proxy definitions are found in the previous Windows system configuration options. Run the following command in a command prompt to set a WinHTTP proxy definition. Substitute <ip_address_or_domain> and <port> with the necessary values as shown:

netsh winhttp set proxy <ip_address_or_domain>:<port>

If you need to specify exclusions, append the previous command with an exclusion list according to the following syntax. Substitute instances of <exclusion> with the necessary values and delimit multiple exclusions with a ; as shown:

netsh winhttp set proxy <ip_address_or_domain>:<port> "<exclusion1>;<exclusion2>"


You can also mass-deploy WinHTTP proxy definition settings with a Group Policy. See the following Microsoft TechNet blog post for more information and instructions:

Given all these system-level proxy configuration options, the agent also follows a Windows-specific obedience hierarchy:


Windows Proxy Definition Source


Automatically detect settings checkbox


Use automatic configuration script checkbox and field


Use a proxy server for your LAN checkbox and fields


In "Proxy Settings" window, "Secure" fields and "Exceptions" field


WinHTTP proxy-server and bypass-list settings


Configure proxy definitions in the "Proxies" tab:

  1. Click System Preferences.
  2. In the "System Preferences" window, click Network.
  3. In the "Network" window, click Advanced.
  4. Click the Proxies tab.
  5. Select the Secure Web Proxy (HTTPS) option.
  6. Specify an address in the "Secure Web Proxy Server" field.
  7. Specify any exceptions as necessary.