Install & Configure Syncthing for Seamless Master‑Slave File Sync
This guide walks you through downloading Syncthing, setting up a master server, configuring access credentials, adding and syncing folders, deploying slave servers, linking devices, and testing bidirectional synchronization, complete with screenshots and tips for ensuring reliable file replication across Windows, Linux, macOS, and Android platforms.
1. Overview
Syncthing is a free, open‑source, cross‑platform file‑synchronization tool that runs on Windows, macOS, Linux, Android and even on routers or Raspberry Pi. It provides a web UI and supports a Chinese interface.
2. Download
Official download page: https://syncthing.net/downloads/ . Choose the package that matches your operating system.
3. Install the master server
Extract the archive and double‑click the executable. The management page opens automatically, usually at http://127.0.0.1:8384/, and HTTPS connections are supported.
4. Master configuration
Set the access address, username and password.
Add a synchronization folder, give it a custom name and directory. If the shared folder does not exist, Syncthing automatically creates a .stfolder directory.
Configure the synchronization interval as needed.
After configuration, the status shows a non‑shared state because no other server is connected yet.
5. Deploy the slave server
Install Syncthing on the slave machine using the same download method. After installation, open the web UI and note the device ID displayed on the master server (e.g.,
NQIYOJG‑TNHCUH7‑44XX6D5‑452FZNU‑GODB7PH‑M5B3OTU‑QETJNOG‑TMVW3QZ).
On the slave, add the master as a remote device by entering the master’s device ID.
The slave shows “not connected” until the master confirms the addition.
6. Configure folder synchronization
On the master, edit the folder settings and select the slave server (do not enable encryption if you want plain file sync).
After saving, the status changes to “syncing”.
On the slave, add the same folder.
When synchronization completes, the master’s files appear in red and the slave’s original files remain, indicating successful bidirectional sync.
7. Synchronization testing
Tests confirm that:
Synchronization is bidirectional.
File and folder deletions propagate both ways.
File modifications are synchronized.
The sync interval can be adjusted as needed.
Log details can be viewed in the web UI.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Raymond Ops
Linux ops automation, cloud-native, Kubernetes, SRE, DevOps, Python, Golang and related tech discussions.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.