Agent Connection Diagnostics
If any of your Insight Agents experience connection issues or other errors, you can check the connectivity of the agent to troubleshoot the problem. The Insight Agent service features a connection diagnostics command that you can run to verify several points of the connection’s journey to the Insight platform.
- Agent Connection Diagnostics
This connection diagnostics test consists of four to five individual checks, depending on the presence of a configured proxy for the agent or an explicit proxy command argument. These checks include:
- Socket Connection
- HTTP CONNECT (when a proxy is detected or explicitly passed)
- Agent Ping
- TLSv1.2 Handshake
- Agent Message
All checks must pass for the overall connection diagnostics test to pass.
The connection diagnostics test must execute from a terminal (Mac or Linux) or a command prompt (Windows) with the current directory set to the version subfolder of the Insight Agent installation directory. Ensure that the current directory of your terminal or command prompt is set to the correct location. Default installation directories are as follows.
Check your current directory
-diagnose command detailed below will not execute unless your command line interface is set to an Insight Agent version subfolder. Make sure your current directory is properly set before continuing.
Windows Default Directory
1C:\Program Files\Rapid7\Insight Agent\components\insight_agent\agent_version_number
Mac and Linux Default Directory
See the following example commands for each operating system.
Windows Example Connection Diagnostics Test
1ir_agent.exe -diagnose -region us-east-1 -proxy https://user:firstname.lastname@example.org:8443
Mac and Linux Example Connection Diagnostics Test
1./ir_agent -diagnose -region us-east-1 -proxy https://user:email@example.com:8443
The options of this command are defined as follows:
-diagnose- Required. This initiates the connection diagnostics test.
-region- Required if your data region is not United States - 1. The
-regionoption allows you to specify your appropriate data region as a test target for the agent. If you omit this option from the command, the test target defaults to
us-east-1. If your data region is not United States - 1, include the
-regionoption with one of the following region codes:
- United States - 2 -
- United States - 3 -
- Canada -
- Europe -
- Japan -
- Australia -
- United States - 2 -
-proxy- Optional. The test can automatically identify and account for proxies that the agent is configured to use, but you can use the
-proxyoption to explicitly test against a proxy address of your choice. These example commands include basic authentication (
user:password@) for syntax purposes, but authentication is not required for the test to run.