Resilio Agents don't connect to Management Console

Overview

If you installed Resilio Management Console and followed the steps to install and connect Agents, but still do not see your Agents on the Agents tab, follow these steps to troubleshoot connectivity issues.

1. Check that Resilio Agent process is running.

OS X: Open Activity monitor and search for Resilio Connect Agent process.
Windows: Press "Win+R", type services.msc. In the list of services, search for Resilio Connect Agent Service and make sure it's running. Try restarting it.

Linux: In Terminal, run ps aux | grep agent. If the Agent process is up and running, you will see a corresponding line.

vboxuser@ubuntu-25-10:~/apps/resilio-agent$ ps aux | grep agent
vboxuser    2087  0.0  0.1  97536  7468 ?        Ssl  13:22   0:00 /usr/libexec/gcr-ssh-agent --base-dir /run/user/1000/gcr
vboxuser    2091  0.0  0.1  10632  6604 ?        Ss   13:22   0:00 /usr/bin/ssh-agent -D
vboxuser    3047  0.0  4.7 1179708 258112 ?      Sl   13:23   0:04 /usr/bin/gnome-text-editor /etc/resilio-agent/sync.conf
vboxuser    3175  0.0  0.1 240080  7824 ?        Ssl  13:24   0:00 /usr/libexec/ptyxis-agent --socket-fd=3 --rlimit-nofile=1024
root        5308  0.6  0.6 833212 32912 ?        Ssl  14:04   2:49 ./rslagent --config /home/vboxuser/Downloads/sync.conf --after-restart --background
vboxuser    8055  0.0  0.0  18148  2584 pts/0    S+   21:46   0:00 grep --color=auto agent

If the Agent process is not running, try to start it manually:

Agent installed from a tarball archive

sudo ./rslagent --config /path/to/sync.conf

Agent installed from a DEB/RPM package
```
sudo systemctl start resilio-agent
```

2. Make sure the configuration file is present.

Note

Applicable to scenarios where Agents are configured to use a configuration file. If your Agents connect by providing an IP address, skip to step 4.

If the Agent process is running but the Agent doesn't connect, check the following directories for the sync.conf file:

OS X: /Users/<username>/Library/Application Support/Resilio Connect Agent
Windows: C:\Program Files\Resilio Connect Agent
Linux: the location of the sync.conf file is provided in the --config startup parameter.

If the configuration file is missing, re-download it from Management Console.

3. Analyze configuration file.

If the configuration file is present and used by the Agent, make sure it conforms to JSON format and contains the correct values for:

Console's address (host)
Bootstrap token (bootstrap_token)
Certificate fingerprint (cert_authority_fingerprint)

Compare the values in the configuration file with the values in Management Console > Settings and Advanced settings.

{
  "management_server": {
    "host": "192.168.0.110:8444",
    "cert_authority_fingerprint": "5f18273b02e98d25726ad528583056293ea7e5bad240286dd55770bd8a443183",
    "bootstrap_token": "V35IGHYQBINTHR5ONKLOTXDFBDZXJANYQB5PJICYFKUD5ANCL5KQ",
    "disable_cert_check": false
  },
  "mc_restricted_access": false,
  "use_gui": true
}

4. Ensure Agents that connect by explicitly providing a host address use the correct address.

Verify the address in the Agent UI settings (Windows and macOS) or the one that you provide in the --server parameter (Linux) is correct.
Select Agents > Agents Pending Approval to check if the Agent is listed on the list of Agents pending approval.
Verify if the Agent hasn't been removed from the Managmenet Console and try recovering it.

5. Check network connection between Agents and the Management Console.

Make sure that ports and protocols are properly configured and not blocked, and that the firewall rules have been added to allow network traffic between the participating hosts.

Note

If you use the Management Console's hostname in the Agent's configuration file, verify the Agent can resolve it to the correct IP address.

Check network using `netcat`

Use netcat to check if the Management Console is listening on the correct port (default is 8444). If not, check the Management Console logs for errors.

On the host running the Management Console, stop the Management Console service, then start netcat:
- Windows: nc -L -p 8444
- Linux: nc -l -p 8444
On the Agent, start netcat to connect to the Management Console:
- Windows: nc <ip> 8444
- Linux/macOS: nc <ip> 8444
where <ip> is the Management Console's IP address or DNS name.
On the Agent, type some text and press Enter. If the connection is successful, you should see the text on the Management Console host. If not, check the network configuration and firewall rules.

On the Agent, you can also check the established connection with netstat:

Windows: netstat -an | find "8444"
Linux/macOS: netstat -an | grep 8444

vboxuser@ubuntu-25-10:~/apps/resilio-agent$ netstat -an | grep 8444
tcp        0      1 192.168.0.76:56872      192.168.0.110:8444      SYN_SENT   
tcp        0      0 192.168.0.76:57226      192.168.0.110:8444      ESTABLISHED

Check network using `telnet`

You can also use telnet to verify that you can connect from the Agent host to the Management Console:

telnet <ip> 8444

where <ip> is the Management Console's IP address.

6. Verify if the Agent hasn't been removed from the Managmenet Console.

If this is not a clean installation, the Agent may have been connected to the Management Console previously and then removed. To verify that, select Settings > Removed Agents and check if the Agent is on the list.

Recover the Agent, then restart the Agent service to re-establish connection to the Management Console. For more information, see Removing Agents from Management console, restoring the removed Agents.

If none of these tips helps, collect logs from the Agent and the Management Console and open a support ticket.