Skip to main content

Network

Stratora's network requirements are intentionally narrow. Most environments will only need to confirm two things: that the Server is reachable on port 443, and that each Collector can reach its assigned devices on the protocols it polls them with.

Required ports — at a glance

Operator → Server

SourceDestinationPort / ProtocolPurpose
Operator workstationsStratora Server443 / TCP (HTTPS)Web UI

Stratora Server inbound

SourceDestinationPort / ProtocolPurpose
Operators, Agents, CollectorsStratora Server443 / TCP (HTTPS)All UI traffic, agent enrollment and heartbeat, collector config pulls and metric ingest
Internet (only during cert issuance)Stratora Server80 / TCP (HTTP)Optional — required only if you use HTTP-01 certificate issuance during initial setup

Stratora's internal services (the backend API, the time-series database, and PostgreSQL) all bind to loopback only and are not exposed to the network. You do not need to open any other inbound port to the Server.

Agent → Server

SourceDestinationPort / ProtocolPurpose
Each monitored host running the Stratora AgentStratora Server443 / TCP (HTTPS)Enrollment, heartbeat, configuration pull, metric push

Agents are push-only. They never listen for inbound traffic. They also do not honor HTTP_PROXY or HTTPS_PROXY environment variables in this release — each agent host must have direct outbound HTTPS reachability to the Server.

Collector → Server

SourceDestinationPort / ProtocolPurpose
Each Collector (local or remote)Stratora Server443 / TCP (HTTPS)Configuration pull, heartbeat, metric push

Collector → monitored devices

SourceDestinationPort / ProtocolPurpose
CollectorAny monitored deviceICMP Echo RequestReachability and latency probes (the Response column on the Nodes list)
CollectorSNMP-monitored device161 / UDPSNMP polling (v2c and v3)
CollectorvCenter or ESXi host443 / TCP (HTTPS)vSphere API
CollectorHTTP / HTTPS endpoint80 / TCP or 443 / TCPEndpoint monitoring

What Stratora does not do

  • No SNMP traps. Stratora polls SNMP-monitored devices; it does not listen on UDP/162 for traps in this release.
  • No outbound proxy support on the agent. The agent's HTTP client does not honor HTTP_PROXY / HTTPS_PROXY. Plan on direct outbound HTTPS from each monitored host.

Where to go next