Installing proxy server and connecting it to Management Console

Resilio Connect Proxy is supported for Windows and Linux OS, x64 both. 

See system requirements here. 
Proxy is capable of handling up to 20 million files and 2 thousand agents without significant performance degradation.

Basic schema with proxy involved in illustrated below
(image is clickable)

Prior to installing a Proxy, some preparations will be required: 

Forward ports in the firewalls

By using the Connect Proxy you don’t need to have any open ports for incoming connections on the corporate firewall. You need to have these outgoing ports

Agents installed in WAN

Agents installed in LAN

Proxy server installed in DMZ

Tracker server installed in DMZ or in WAN

If several proxy servers are configured, they will work in load balancing mode. High availability of proxy servers is not supported.

First configured proxy will be used for Agents to connect to the Management Console by default, unless specifically instructed otherwise. 

 See this guide to configure Agents to use proxy connection.

To install Resilio Connect Proxy, follow the steps below.

WINDOWSLINUX

Download Resilio-Connect-Agent_x64_proxy.msi. Start the msi and complete the installation. The Proxy will be installed into C:\Program Files\Resilio Connect Agent Proxy directory, register a new service and listen on port 1080 awaiting connection from the Management Console On the Management Console go to Settings -> Auxiliary Servers and click "Add proxy" button. Fill in the IP or DNS name of the server where the Proxy was installed, IPv6 is supported. Keep the default port 1080.

Additionally it's possible to install a tracker server on the same computer as proxy. Option to add a tracker server, if checked, automatically adds tracker configuration to the Management Console.
Note, the tracker server must be installed manually!
Note, this checkbox only works if tracker uses default port 3000. 

Checking tracker as 'default' can ease further utilization of tracker 

Management Console will create socks5 tunnel to the Proxy. If all was set correctly, test connection will be successful and you'll be redirected to Configuration tab.


Bind port: data traffic port between agent, that proxy listens on. Can be changed manually and be different from default 3328 if it's necessary to route traffic internally. The port can be pre-filled from the configuration file.
Proxy available at: it's pre-filled from the IP of the proxy entered on previous step with the default interface port 3328 that the agent binds to, and port 12345 that the proxy listens to locally. If necessary, fill in another interface and click "+".  
Define local subnets: the networks to and from which proxy will route traffic. Click "+" to add it. Can be pre-filled from configuration file. Can be in format ip/mask or ip/bits

Once configured, the proxy will appear in the table. It may take a few seconds for it to be marked with a green dot though. 

See here to learn how to use it further for the data traffic.

Download and unpack resilio proxy tar. Run the binary with command
./rslproxy --config /path/to/sync.conf --proxy 
Argument --config optional. If configuration file contains parameter "proxy_server_enabled": true, no need to add  --proxy to start command. Otherwise, --proxy parameter is compulsory.
The process will start and listen on port 1080 by default.

On the Management Console go to Settings -> Auxiliary Servers and click "Add proxy" button. Fill in the IP or DNS name of the server where the Proxy was installed, IPv6 is supported. Keep the default port 1080.

Additionally it's possible to install a tracker server on the same computer as proxy. Option to add a tracker server, if checked, automatically adds tracker configuration to the Management Console.
Note, the tracker server must be installed manually!
Note, this checkbox only works if tracker uses default port 3000. 

Checking tracker as 'default' can ease further utilization of tracker 

Management Console will create socks5 tunnel to the Proxy. If all was set correctly, test connection will be successful and you'll be redirected to Configuration tab.

Bind port: data traffic port between agent, that proxy listens on. The port can be pre-filled "listening_port" from the configuration file with parameter , as illustrated on the screenshot.
Proxy available at: it's pre-filled from the IP of the proxy entered on previous step and from the listening port in configuration file. If necessary, fill in another interface and click "+". 
Define local subnets: the networks to and from which proxy will route traffic. Click "+" to add it. Can be pre-filled from configuration file. Can be in format ip/mask or ip/bits

Once configured, the proxy will appear in the table. It may take a few seconds for it to be marked with a green dot though.

See here to learn how to use it further for the data traffic.

The established connection between proxy and the Management Console will be kept open.

Advanced settings can be used to allow routing traffic across WAN.

To re-install Resilio Connect Proxy, follow the steps below.

Reinstalling proxy server requires some additional steps to 

1. Stop Resilio proxy process. 

2. Remove proxy's storage folder 

3. Compulsory step: Delete proxy configuration from the Management Console. If this is not done, new proxy process won't be authorised by the Management Console

4. Install new proxy and connect it to the Management Console.

Not compulsory: prepare configuration file

The file must contain address and connection information to the Management Console. It can be downloaded from the Management Console, having some excessive parameters removed. The minimal config shall contain the following information: 

{
"management_server": {
 "host": "192.168.1.166:8444",
 "cert_authority_fingerprint": "8.....b049",
 "bootstrap_token": "IAL....IL4Q",
  "disable_cert_check": false
  }
}

Additional pre-configured settings can be, but not necessarily must be, added:

"listening_port": 12345  //the port for data traffic between agents. Proxy will bind on this port on external network interface
"proxy_server_local_addrs": [ "192.168.1.0/24" ]   //subnets through which the traffic shall go indirectly through proxy, inside and outside
"proxy_server_enabled": true  //can be used for a proxy installed on a Linux