Proxy Settings

Some organizations’ security policies dictate routing outbound traffic from internal networks to the internet via a proxy server.

SEI agents support HTTP/HTTPS proxy and can be deployed in these organizations to monitor HTTP/HTTPS targets.

Outbound ICMP, UDP traffic, and inbound agent-to-agent probing cannot be routed through the proxy.

Click to expand

Environment variables

Configure proxy settings by setting the following environment variables:

Proxy Environment Variables


Used for HTTP Traffic (e.g. HTTP_PROXY=


Used for HTTPS Traffic (e.g. HTTPS_PROXY=


Addresses to bypass the proxy servers (e.g. NO_PROXY=localhost)

Proxy configuration by agent type

  • Static Agent for Docker and Cloud Agents
    • Agents run as Docker containers.
    • The proxy can be changed in the host’s Docker runtime environment settings per the instructions provided by the manufacturer of the host.
  • Static Agent for EdgeLQ devices
    • SPEKTRA Edge and generic device like Rasperry Pi4 and Dell VEP edge servers are boot from the EdgeLQ OS.
    • EdgeLQ pod manifest utilizes the same environment variables that can be inherited from the EdgeLQ configuration.
    • EdgeLQ proxy settings are controlled through the API and configured by the channel partner.
  • Mobile Agents for Windows and macOS
    • SEI Mobile Agent uses the system’s default proxy settings by default.
    • The bypass addresses are always configured to ‘localhost’.
    • Override the proxy settings in the agent interface. Settings -> Advance -> Network Proxy.
Click to expand

In This Article