Skip to content

Ports Protocols Required by Resilio Active Everywhere

Resilio Active Everywhere uses specific ports and protocols to properly function. Depending on the network your Agents are in, these must be open to let traffic flow between the Agents, Management Console, and the Tracker Server. The Management Console communicates with the Agents using TCP.

Once the Management Console and Agents are communicating, the Resilio Active Everywhere Agents must also be able to transfer data to and from other Agents. Agents transfer data to each other using TCP and UDP. To make this possible the necessary ports must be opened and forwarded on all firewalls, NATs, and routers between the Agents.

The table below contains default values for the ports used by Resilio Active Everywhere. Ports can be customized in Management Console configuration file and the profile.

Ports

Management Console

Port Protocol Description
8443 TCP Management Console web interface.
8444 TCP Resilio Agent control traffic.
8445 TCP Resilio Agent events and logs.
Note: Port 8445 is optional and only used when Management Console saves events to events.log.
8446 TCP API gateway.
Note: Required for new installations v3.8.0 by default. For MC updated from previous version it's required only if enabling the API gateway in the configuration file.
3000 TCP and UDP (incoming) Tracker service.
Note: By default, the tracker runs on the same machine as the Management Console, but it can be placed on another machine if preferred.
1080 TCP (outgoing) Connection to Resilio Proxy

Info

Additionally, Management Console reaches out to the following Resilio's public servers:

  • Address https://connect-license.resilio.com/check_connect.php on port 443
    Checking license updates. Every 24 Hours or upon service startup. If there are unlicensed Agents, the Management Console checks for license updates every 10 minutes.

  • Address https://upload.resilio.com/up on port 443
    Create Support Case (with automated Log upload). Manual log uploads go to https://feedback.resilio.com/ which is a link to https://upload.resilio.com/up

Agent

Port Protocol Description
3000 TCP and UDP (outgoing) Tracker Server
Note: UDP is optional and if your organization doesn't allow it the Tracker will still work.
3839 TCP and UDP Data transfer between agents.
Note: If each of the Agents is behind a NAT or firewall (pfSense in particular), it may required to:
  • Set up port forwarding for at least one of agents.
  • Configure external port. Add custom parameter external_port with a port number to the Agent's Profile. Otherwise, it's not guaranteed that the outgoing traffic will be forwarded through the same data transfer port, which will make connection impossible between such Agents.
Note: Connect Agents can be configured to transfer data using only TCP or UDP if your organization limits the transmission of one these protocols
3838 Multicast UDP (239.192.0.0) LAN agent discovery.
Note: Multicast is optional and if your organization doesn't allow it there are other ways to enable Connect Agents to transfer data.
1900 UDP multicast to 239.255.255.250 UPnP and NAT-PMP.
Note: Multicast is optional and if your organization doesn't allow it there are other ways to enable Connect Agents to transfer data.
5351 TCP unicast
3328 TCP and UDP Connection to Proxy server.
Note: Additional custom port might be required. For details, see Installing Proxy Server And Connecting It To Management Console.

Proxy Server

Note

Applicable only to deployments with Proxy Servers.

Port Protocol Description
1080 TCP (incoming) Connection from Management Console
3328 TCP and UDP (incoming) Connection from agents to proxy server. Additionally, a custom port might be required. For details, see Installing Proxy Server And Connecting It To Management Console.

Port Forwarding

If your Management Console (and default Tracker Server) are behind a Firewall and you have WAN based Agents, you may need to enable port forwarding from you WAN based IP address to your LAN based computer (hosting the Management Console) for the following:

Port Protocol Description
8444, 8445 TCP Management Console
3000 TCP and UDP Tracker Server

Diagrams

Basic Configuration

In a basic deployment scenario, the Management Console, Tracker and Agents are on the same network.

Basic deployment

Advanced Configuration

In an advanced deployment scenario, the Management Console and the Tracker are behind a firewall while the Agents are distributed and communicate over WAN.

Advanced deployment

Agent Connection to Management Console

For Resilio Agents to communicate with the Management Console, they require the sync.conf configuration file which contains the IP address (or DNS name), and security credentials of the Management Console. This is so they can:

  • Establish a secure connection to the Management Console.
  • Send file and job operation events.
  • Connect to other Agents and receive Agent policy.