Failed to load required data.
Please contact support.

Important:Resilio Agents 3.6 and newer require an upgraded Resilio Management Console for compatibility. Ensure you update the Management Console before upgrading any Agents. Agents won't be available for download until the Management Console is updated.

By checking this box I confirm that the Resilio Management Console is already updated to the latest version before proceeding with the update of Resilio Agents.

Version    

Please read the change log before you update to a new build. Read Changelog

Management Console

Important: please ensure you update the Management Console before upgrading any Agents.

Learn More About Installing the Management Console

Management console is running under resilio user inside container and this user has UID=555 and GID=555. Make sure that storage folder has owner and group 555 on host system.
$ sudo addgroup --gid 555 resilio
$ sudo adduser --uid 555 --ingroup resilio --disabled-password --gecos "" resilio

$ mkdir mc_data
$ sudo chown 555:555 ./mc_data
Then run the container:
$ sudo docker run -d -v $(pwd)/mc_data:/home/resilio/resilio-connect-server/var \
       -v /etc/localtime:/etc/localtime:ro \
       -p 8443:8443/tcp \
       -p 8444:8444/tcp \
       -p 8445:8445/tcp \
       -p 8446:8446/tcp \
       -p 3000:3000/tcp \
       -p 3000:3000/udp \
       -p 3839:3839/tcp \
       -p 3839:3839/udp \
       -p 3838:3838/tcp \
       -p 3838:3838/udp \
       --restart=always \
       resilio/mc:.no_agent
Or you can run container using docker-compose. Create docker-compose.yml file with the following content:
version: '3'

services:
  resilio_connect_mc:
    stop_grace_period: 10m
    image: resilio/mc:.no_agent
    volumes:
      - ./mc_data:/home/resilio/resilio-connect-server/var
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 8446:8446/tcp
      - 8445:8445/tcp
      - 8444:8444/tcp
      - 8443:8443/tcp
      - 3000:3000/tcp
      - 3000:3000/udp
      - 3838:3838/tcp
      - 3838:3838/udp
      - 3839:3839/tcp
      - 3839:3839/udp
    restart: always
Docker on linux allows you to run container in a host network mode, so there will be no separate isolated network stack the container works with, it will use network stack of the host system. Example:
version: '3'

services:
  resilio_connect_mc:
    stop_grace_period: 10m
    image: resilio/mc:.no_agent
    network_mode: "host"
    volumes:
      - ./mc_data:/home/resilio/resilio-connect-server/var
      - /etc/localtime:/etc/localtime:ro
    restart: always
Save file and run container:
$ sudo docker-compose up -d

Desktop & Server Agents

Important #1: please ensure you update the Management Console before upgrading any Agents.

Important #2: starting with 3.6 version, Agent encrypts vital data in its storage folder by default, so it must be launched with environment variable RESILIO_KEY with some key value that will be used for encryption/decryption.

Learn More About Installing Desktop Agents & Connecting It to The Management Console...

Important: starting with 3.6 version, Agent encrypts vital data in its storage folder by default . Docker container must be launched with environment variable RESILIO_KEY with some key value that will be used for encryption/decryption. Dump this env var into a file (using syntax RESILIO_KEY=SecureKeyForEncryption) and place it in a secure location:
echo RESILIO_KEY=SecureKeyForEncryption > /path/to/safe/location/resilio_enc_key.env
Use this file to launch docker container with --env-file option.


Agent is running under resilio user inside the container and this user has UID=555 and GID=555. Make sure that mounted folders have 555:555 permissions.
$ mkdir /path/to/dir/to/be/shared
$ mkdir /path/to/agent/storage/folder

$ sudo chown -R 555:555 /path/to/dir/to/be/shared
$ sudo chown -R 555:555 /path/to/agent/storage/folder
Then run the container:
$ sudo docker run -d -p 3839:3839/tcp \
       -p 3838:3838/tcp \
       -p 3839:3839/udp \
       -p 3838:3838/udp \
       -v /path/to/sync.conf:/home/resilio/sync.conf \
       -v /path/to/dir/to/be/shared:/home/resilio/shared \
       -v /path/to/agent/storage/folder:/home/resilio/.sync \
       -v /etc/localtime:/etc/localtime:ro \
       --restart always \
       --env-file /path/to/safe/location/resilio_enc_key.env \
       resilio/agent:
Docker on linux allows you to run container in a host network mode, so there will be no separate isolated network stack the container works with, it will use network stack of the host system. Example:
$ sudo docker run -d --network host \
       -v /path/to/sync.conf:/home/resilio/sync.conf \
       -v /path/to/dir/to/be/shared:/home/resilio/shared \
       -v /path/to/agent/storage/folder:/home/resilio/.sync \
       -v /etc/localtime:/etc/localtime:ro \
       --restart always \
       --env-file /path/to/safe/location/resilio_enc_key.env \
       resilio/agent:
Or you can run the container using docker-compose. Create docker-compose.yml file with the following content:
version: '3'

services:
  resilio_connect_agent:
    stop_grace_period: 3m
    image: resilio/agent:
    env_file:
      - /path/to/safe/location/resilio_enc_key.env
    volumes:
      - /path/to/sync.conf:/home/resilio/sync.conf
      - /path/to/dir/to/be/shared:/home/resilio/shared
      - /path/to/agent/storage/folder:/home/resilio/.sync
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 3839:3839/tcp
      - 3838:3838/tcp
      - 3839:3839/udp
      - 3838:3838/udp
    restart: always
Or if you'd like to run the container in host network mode:
version: '3'

services:
  resilio_connect_agent:
    stop_grace_period: 3m
    image: resilio/agent:
    network_mode: "host"
    env_file:
      - /path/to/safe/location/resilio_enc_key.env
    volumes:
      - /path/to/sync.conf:/home/resilio/sync.conf
      - /path/to/dir/to/be/shared:/home/resilio/shared
      - /path/to/agent/storage/folder:/home/resilio/.sync
      - /etc/localtime:/etc/localtime:ro
    restart: always
Save file and run container:
$ sudo docker-compose up -d

NAS Agents (packages)

Important: Please upgrade your Management Console before upgrading agents.

Learn More About Installing Desktop Agents

Didn't find package for your NAS? Please contact our support

Android Agents

Important: please ensure you update the Management Console before upgrading any Agents.

Learn More About connecting Android Agents the Management Console

File Locking Driver

It's a minifilter driver designed to manage file locking and synchronize access to files, preventing conflicting operations.

Proxy Server

Important: please upgrade your Management Console before upgrading proxy.

Learn More About Installing Proxy Server

Tracker Server

A Tracker server is automatically installed with the Management Console. Use these installers if you wish to setup a separate Tracker server instance and configure Resilio Agents to connect to it.

Learn More About Installing & Configuring Tracker Server

Tracker doesn't require any folder to be mounted since it doesn't store any data on disk while running.
Run the container:
$ sudo docker run -d -p 3000:3000/tcp \
       -p 3000:3000/udp \
       -v /etc/localtime:/etc/localtime:ro \
       --restart always \
       resilio/tracker:
Important: on Linux you can run container in host:
$ sudo docker run -d --network host \
      -v /etc/localtime:/etc/localtime:ro \
      --restart always \
      resilio/tracker:
In order to run the container using docker-compose, you need to create docker-compose.yml file with the following content:
version: '3'

services:
  resilio_connect_tracker:
    stop_grace_period: 2m
    image: resilio/tracker:
    ports:
      - 3000:3000/tcp
      - 3000:3000/udp
    volumes:
      - /etc/localtime:/etc/localtime:ro
    restart: always
Or in host network mode:
version: '3'

services:
  resilio_connect_tracker:
    stop_grace_period: 2m
    image: resilio/tracker:
    network_mode: "host"
    volumes:
      - /etc/localtime:/etc/localtime:ro
    restart: always
Save file and run container:
$ sudo docker-compose up -d

API Documentation