Running the Agent Behind a Proxy or Firewall
The outbound network access the SeqOps server agent needs, and why no inbound rules are required.
The SeqOps server agent needs outbound HTTPS only. It needs no inbound firewall rules, no open ports, and no cloud credentials on the server.
Required Outbound Access
- •HTTPS (port 443) to the SeqOps server address in the install command from Server → Activation (the value after
--server-url). - •HTTPS to Amazon S3 — agent profile downloads are redirected to time-limited Amazon S3 links, so the server must be able to reach S3 over HTTPS.
What the Agent Does Not Need
- •Inbound firewall rules — The agent opens every connection itself, outbound. Nothing needs to connect in to the server.
- •Open listening ports — The agent does not accept incoming connections.
- •Cloud credentials — The server holds only its own agent registration. Cloud environments are connected separately, with read-only credentials entered in SeqOps.
Behind a Proxy
- •Linux and the Windows agent read the machine-wide
HTTPS_PROXYandNO_PROXYenvironment variables. - •The Windows updater uses the system (WinINET) proxy setting instead.
If the proxy blocks this traffic, the agent can't connect and the server shows as offline.
Need Help?
If the agent can't connect after the firewall and proxy allow this traffic, see Agent Shows Offline: Step-by-Step Diagnosis or contact support@seqops.io or use the Contact Us page.