Locate the MC Configuration File
Configuration file “resilio-connect-server.conf” is stored in different locations depending on OS:
Windows (starting from 2.5 version): C:\ProgramData\Resilio\Connect Server\resilio-connect-server.conf
Linux: ${resilio_connect_server_dir}/var/resilio-connect-server.conf
Notes
It is in JSON format, so please stick to JSON syntax to ensure Resilio Connect Management Console can parse the file successfully.Management Console must be stopped before editing the configuration file.
Below are most commonly used parameters in the configuration file.
Sections & Parameters in the Config File
"loggers" section
Keeps settings for different log files rotation
Field |
Default value |
Purpose |
|
|
In bytes. The size of debug log (common.log). When it reaches this size, it's archived. |
|
|
Number of archived log files that Console keeps. Older ones are deleted for good. |
|
|
New events are added to 'filename' in descending order. |
“events_server” section
Event logger logs all the file operations performed by Agents on all clients. Read more about events and logging here.
Field |
Default value |
Purpose |
|
|
Maximum amount of files stored by event logger |
|
|
Protocol used by clients to connect to event server |
|
|
Maximum file size. When exceeded, event logger will create a new file, up to maxFiles |
|
|
Interface used by event logger for incoming connections. 0.0.0.0 and :: means logger is listening on all available interfaces for IPv4 and IPv6 accordingly |
|
|
Port used by event logger for incoming connections |
“peerServer” section
peerServer section contains settings used by clients to connect, report status and receive a new set of settings from the Connect Management Console.
Field |
Default value |
Purpose |
|
|
Path to Management Console custom certificate and private key, used for establishing SSL connection. Read more on using custom certificate and key here. The section also contains information about cipher suits used for securing connection between Agents and MC. Some ciphers are deprecated for clean installation of MC v4.1.0. Read more about it here. |
|
|
Interface used by Connect Management Console for incoming connections. 0.0.0.0 and :: means Console is listening on all available interfaces for IPv4 and IPv6 accordingly |
|
|
Port used by Connect Management Console for incoming connections |
“https” section
https section contains settings used by admin to connect to the Connect Management Console WebUI.
Field |
Default value |
Purpose |
|
|
Path to Management Console custom certificate and private key, used for accessing WebUI over SSL. Read more on using custom certificate and key here. The section also contains information about cipher suits used for securing connection to MC WebUI. Some ciphers are deprecated for clean installation of MC v4.1.0. Read more about it here. |
|
|
Interface used by WebUI for incoming connections. 0.0.0.0 and :: means Management Console is listening on all available interfaces for IPv4 and IPv6 accordingly |
|
|
Port used by WebUI for incoming connections |
“backup” section
backup section contains settings on backing up all Resilio Console data as well as cleanup schedule.
Field |
Default value |
Purpose |
|
|
Time in days for storing backups |
|
|
Schedule to clean up old backups |
|
|
Schedule to perform backups |
|
|
Backups location |
The "0 0 6 * * *" is a way to schedule a task very similar to the one in crontab with the only difference that values are "second, minute, hour, day of month, month, day of week". So the "0 0 6 * * *" indicates to make a daily backup at 6am.
“reporting” section
Field |
Default value |
Purpose |
dir |
data/reporting/daily |
Name of the directory where event databases are stored |
|
1209600000 (N_Days_a_Year * Miliseconds_a_Day) |
Number in milliseconds for how long event databases are stored. Put this parameter on next level below "reporting". |
"usersSecurity" section
visible in config for clean installation of v2.11. can be added manually to config for updated Management Console
Field | Default value | Purpose |
passwordExpirationDaysPeriod |
120 |
Sets the expiration of user's password, in days. Values lesser than 1 day or greater than 1825 days (5 years) are not allowed and will be treated as "120 days" instead. |
numPreviousPaswordsChecks |
10 |
Number of previously used passwords that will be saved and checked to ensure unique password policy. Read more about passwords here. |
"diskSpaceLevels" section
Controls when the warnings about lack of free space on the server appears. It will appear when either of the thresholds (space or ratio) is reached first. When "low" warning appears, Agents will only send "error" type of events. When critical error appears, no events are sent by the Agents.
Field | Default value | Purpose |
|
1073741824 for low 536870912 for critical
|
In bytes. When that many free bytes are left on the storage, MC will give a warning (low) or an error (critical) accordingly. |
ratio |
|
If there's only 5% or 2% of free space left, MC will a warning (low) or an error (critical) accordingly. |
"apiGateway" section
Available starting with MC v3.8.0. Enabling API gateway allows to scale requests and preserves performance on highly-loaded flows.
Field | Default value | Purpose |
|
true
|
It's enabled by default for new MC installations. For updated MC it's disabled. |
|
8446 0.0.0.0 |
By default, the API worker listens on port 8446 all interfaces. |
Other sections and section-less params
-
winston
section is used for Connect Management Console and database logs. It is advised not to change default values. -
logs-storage
value contains the relative path to the store debug logs collected by the Management Console from Agents. -
db
section contains path to the Connect Management Console database. -
system
section contains path to file, where Connect Management Console records its PID when started. -
agentWorkers
- allows to add workers to the main MC process for heavily loaded system. Read here for more details. -
security
- section is missing by default. Can be added in config file to address the following:- disable local user accounts. Read here for more details
- enable CSP (v4.1.0 and newer)
{ "security": { "contentSecurityPolicyHeader": true } }