Skip to Content
Resilio Sync

Resilio Sync

Peer-to-peer file synchronization built on the BitTorrent protocol, managed and sandboxed by QuickBox Pro.

Overview

Resilio Sync (formerly BitTorrent Sync / Btsync) is a proprietary, peer-to-peer file synchronization tool that uses the BitTorrent protocol to keep folders in sync across multiple devices. On QuickBox Pro, Resilio Sync is deployed as a managed service with nginx reverse proxy, opinionated storage paths, and a per-user systemd service.


When to Use Resilio Sync

Symptoms

  • Need to keep large media or data folders synchronized between multiple servers or desktops
  • Prefer peer-to-peer sync without relying on centralized cloud storage providers
  • Want LAN-speed transfers with end-to-end control over your files
  • Need a sync solution that can run continuously on a QuickBox Pro host

Resolution

  • Use Resilio Sync to mirror libraries between QuickBox and other devices
  • Avoid third-party cloud storage and keep data on hardware you control
  • Leverage the BitTorrent protocol for efficient, swarm-based transfers
  • Manage the service lifecycle from the App Dashboard (or the equivalent qb CLI) with systemd integration

Key Features on QuickBox Pro

Opinionated Storage Paths

Default storage path at /home/USERNAME/Resilio Sync/storage with managed PID directory under /run/USERNAME.

EULA Acceptance

QuickBox pre-configures agree_to_EULA=yes in the JSON config, so the service can start non-interactively.

Local-Only Web UI Binding

The web UI listens on 127.0.0.1:PORT and is exposed securely via nginx, not directly on the public interface.

Systemd Service Management

Dedicated systemd unit for Resilio Sync with PID tracking and QuickBox integration for status and control.

Reverse Proxy via nginx

nginx configuration is provisioned for you, enabling SSL termination and friendly URLs from your QuickBox host.

Managed lifecycle

Install, reinstall, update, and remove Resilio Sync from the App Dashboard or the equivalent qb CLI.

Proprietary Software Notice

Resilio Sync is proprietary software. By installing it, you agree to Resilio’s End User License Agreement (EULA). QuickBox sets “agree_to_EULA”: “yes” in the generated configuration to allow automated deployment.


Installation

Install from the Dashboard

Open App Dashboard → Package Management (/dashboard?mode=packages), find Resilio Sync in the catalog (browse the File Management category or search), and click Install. The dashboard streams the install log live and Resilio Sync appears in your Application Control panel when it finishes. There is nothing to pick in the dialog — Resilio Sync is a plain, per-user install. Reinstall, Update, and Remove are available from the same panel.

What you see is gated by your account: admins manage any user’s apps; regular users manage their own. See App Management for the full flow.

Install creates the storage path under /home/username/Resilio Sync/storage, generates a user-scoped config with the EULA pre-accepted, registers the per-user systemd service, and provisions the nginx reverse proxy on a QuickBox-managed port.

Install from the CLI (automation)

The CLI runs the same scripts as the Dashboard and is suited to automation and scripting:

qb install btsync -u username qb reinstall btsync -u username qb update btsync -u username qb remove btsync -u username
CommandDescription
qb install btsync -u usernameInstall Resilio Sync for the specified user
qb reinstall btsync -u usernameReinstall while preserving configuration
qb update btsync -u usernameUpdate Resilio Sync to the latest version
qb remove btsync -u usernameRemove Resilio Sync and clean up all files

CLI Options

-u, --usernameRequired

Target QuickBox username for install/remove/update operations

Full flag reference: CLI Reference.

The active config lives at /home/username/.config/Resilio Sync/config.json (web UI bound to 127.0.0.1, EULA pre-accepted) with sync data under /home/username/Resilio Sync/storage. The service runs as resilio-sync@username; manage it with systemctl status resilio-sync@username and journalctl -u resilio-sync@username -f.


Accessing the Web UI

Once installed, Resilio Sync’s web interface is exposed via nginx through your QuickBox host. Exact URLs and ports may vary depending on your configuration, but the common patterns are:

  • https://your-domain.tld/resilio (path-based)
  • https://resilio.your-domain.tld (subdomain, if configured)
Local Bind, Public Proxy

The web UI listens only on 127.0.0.1. External access is provided exclusively through nginx with SSL support and QuickBox hardening. Avoid changing the bind address in the JSON config unless you fully understand the security implications.


Troubleshooting

Resilio Sync runs as a per-user service named resilio-sync@username. Start every diagnosis with the service status and journal:

systemctl status resilio-sync@username journalctl -u resilio-sync@username -f
Symptom: 'resilio-sync@username.service: Failed' or the service won't stay running

The per-user service launches the rslsync binary against the generated config.json. A failed start is usually one of: a missing or malformed config, a storage path that no longer exists, or a stale PID file. Reinstall to regenerate the config, service unit, and binary copy:

qb reinstall btsync -u username systemctl restart resilio-sync@username
Symptom: web UI shows 502 / Bad Gateway or nothing loads at /username/btsync/

The web UI binds only to 127.0.0.1 and is reached through nginx. A 502 means nginx is up but the Resilio process behind it is not listening. Confirm the service is running, then reload nginx:

systemctl status resilio-sync@username systemctl reload nginx

If the service is running but the page is still unreachable, the assigned port may have changed — reinstall regenerates the nginx config and port mapping together: qb reinstall btsync -u username.

Symptom: install fails to download the package / 'fetch failed'

QuickBox installs Resilio Sync from the official Resilio apt repository. If your server cannot reach linux-packages.resilio.com, the version lookup and package download fail and the install aborts. Verify outbound HTTPS connectivity and retry:

curl -I https://linux-packages.resilio.com/resilio-sync/deb/dists/resilio-sync/non-free/binary-amd64/Packages qb reinstall btsync -u username
Symptom: the service starts but won't run because the EULA isn't accepted

QuickBox pre-sets “agree_to_EULA”: “yes” in the generated config so the service starts non-interactively. If you edited the config and removed or changed that line, Resilio refuses to start. Restore it in /home/username/.config/Resilio Sync/config.json, or reinstall to regenerate a clean config.

Symptom: port 8888 already in use

The default web port is 8888, but QuickBox auto-assigns a free port if 8888 is occupied. If two instances collide, reinstall the affected user so a fresh port is assigned and written to both the config and nginx: qb reinstall btsync -u username.


FAQ

A 502 means nginx is reachable but the Resilio process behind it is not listening. Check the service with systemctl status resilio-sync@username, restart it, and reload nginx with systemctl reload nginx. The web UI binds only to 127.0.0.1 and is exposed through nginx, so the process must be running for the proxied page to load.
The per-user service runs the rslsync binary against the generated config.json. A failed start is typically caused by a missing or edited config, a deleted storage path, or a stale PID file. Run qb reinstall btsync -u username to regenerate the config, service unit, and binary, then restart the service.
Resilio Sync is installed from the official Resilio apt repository. If the server cannot reach linux-packages.resilio.com, the version lookup and .deb download fail and the install aborts. Confirm outbound HTTPS works to that host, then re-run qb reinstall btsync -u username.
The active configuration is /home/username/.config/Resilio Sync/config.json. QuickBox pre-accepts the EULA there with "agree_to_EULA": "yes" and binds the web UI to 127.0.0.1. Sync data lives under /home/username/Resilio Sync/storage.

Best Practices

Do

  • Use separate folders per purpose—create dedicated Resilio Sync shares for media libraries, configuration backups, and documents instead of one giant folder.
  • Keep sync targets inside your home or data volumes to avoid permission issues.
  • Monitor disk usage regularly, especially when syncing to smaller VPS plans.
  • Always access the web UI over HTTPS via QuickBox-managed nginx.

Don't

  • Do not point Resilio Sync at system directories like /etc, /var, or /opt.
  • Do not share keys with untrusted devices or users—anyone with a key can replicate the corresponding data.
  • Do not change the web UI bind address from 127.0.0.1 unless you understand the security implications.
  • Do not manually edit QuickBox-managed config templates in /opt/quickbox/config.


Join the Community

Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.

Dedicated Support
Feature Previews
Community Configs
Active Discussions
Join Discord Server
Last updated on