Skip to main content

Firewall Information for the Agent

The Agent makes outbound-only connections to Files.com over standard HTTPS. It operates inside typical enterprise firewall and NAT environments without inbound rules, port forwarding, or exposing internal systems to the public internet.

The Agent uses one network port for data transmission and one for DNS lookup. It does not require any inbound network ports. The Direct Transfers feature is the one exception, adding an optional inbound listener for increased data transmission throughput with the Files.com CLI App and Desktop App.

Data Transmission

The Agent uses a single outbound network port, port 8801, for data transmission. This port cannot be customized.

The Agent uses both the UDP and TCP protocols. It first attempts to connect over the faster UDP protocol and falls back to TCP if UDP is unavailable.

The Agent connects to Files.com using the general pool of Files.com IP addresses. Make sure that outbound connections to these IP addresses using port 8801 are allowed through your firewall.

If your Files.com site uses a custom domain, the Agent connects using your dedicated IP addresses instead.

DNS Lookup

The Agent uses a single outbound network port, port 443, for DNS lookup. This port cannot be customized.

The Agent first attempts to look up public DNS information using https://cloudflare-dns.com. If that connection fails, the Agent falls back to the local host's DNS settings.

Make sure that outbound connections to either https://cloudflare-dns.com or to your designated DNS servers, using port 443, are allowed through your firewall.

Direct Transfers

When Direct Transfers are enabled, allow inbound TCP and UDP connections to the Agent host on the listener ports, which default to 4001 through 4010, and forward each public port to the same port number on the Agent host. The port range and the rest of the listener configuration are set in the Agent configuration file.

When multiple nodes serve the Remote Server for Agent High Availability, every node's host needs inbound rules and port forwarding, and Direct Transfers covers how the port numbers relate across nodes. Clients connect to whichever node is handling their transfer, and a node whose ports stay closed serves its transfers over the standard connection route instead.