Interface schematic

Prev Next

Step-by-step connectivity troubleshooting guides are available in Troubleshooting user and device access.

Diagram illustrating network traffic flow between AWS and Azure components with various controllers and gateways.

NOTE

The LogServer can be interchanged with the LogForwarder

Most communication within the Collective uses TCP port 443. UDP port 443 and UDP port 53 are also required when SPA is used in UDP-TCP mode.


Port 443 usage

Port 443 is used for the following purposes.

Client connections to Controllers and Gateways

Clients — including the Connector and Portal — use port 443 to connect to Controllers and Gateways.

Appliance connections to Controllers

Appliances use port 443 to connect to Controllers. This traffic is low in volume, and network capacity is not a concern even in large deployments. This connection is used for the following:

  1. Health checks. The Controller requests the latest statistics from each appliance so they can be displayed in the admin UI or forwarded to external monitoring systems through SNMP or Prometheus.

  2. Token revocation. When an administrator revokes tokens, the Controller pushes a token revocation list to each Gateway. This immediately forces clients to reestablish their connections, ensuring the Gateway enforces the latest policies.

  3. Configuration updates. When an administrator changes an appliance's configuration, the Controller sends the update to the appliance.

  4. Configuration polling. Each appliance queries the Controller for its current configuration at startup and periodically thereafter, no more than once every 15 minutes. This ensures appliances that were offline when a configuration change was made in the admin UI receive the update when they come back online.

Audit log delivery to the LogServer or LogForwarder

Appliances send audit log records to the LogServer or LogForwarder over port 443. Individual log records are small — approximately 1.5 KB each — but frequency and total volume depend on the size of the deployment. As a planning estimate, allow for one log record per user per second across the entire Collective. For example, 1,000 users on a Gateway produces approximately 1.5 MB/s of log traffic, which represents just over one percent of a 1 GbE NIC's capacity.

Metrics delivery to the Metrics Aggregator

Appliances send metrics to the Metrics Aggregator over port 443. Individual metrics payloads are small, but total volume depends on the size of the deployment.