Although syncthing has a rescan button, sometimes it is necessary to trigger a full rescan. A most common error message is the following:

[GRXBW] 17:53:20 INFO: Puller (folder "nibs", file "Images/Open/wall.png"): dst stat dir: stat /Users/nibs/Images/Open/: no such file or directory

In order to do this, the index directory must be deleted:

Operating System Folder Location
Windows %AppData%/Syncthing/index
Unix ~/.config/syncthing/index
OS X ~/Library/Application Support/Syncthing/index

After the removal of the file, restart syncthing and it will perform a full rescan of the folders.

Synchronising Home Folder

The following sync patterns will prevent synchronising items that have a local state and they are best used for synchronising user home folders.


// ignore dot files
// ignore folders


// include folders

// ignore all the rest

Files that Should Not Be Synchronised

The following files are junk, temporary, trash or state files that should generally not be synchronised:

// Firefox Downloads
// Chrome Downloads
// Safari Downloads

// Temporary / Backup

// OSX

// Linux

// Windows

// BTSync

// Synology

Setting a Different Listen Address and Port

A different listening address and port can be set for syncthing by editing the config.xml file (usually to be found under the user's home directory at ~/.config/syncthing/).

The relevant part of code that refers to the web-interface is the following:

    <gui enabled="true" tls="false">

where is the listening address and 8384 is the port that syncthing listens on.

Limiting CPU and RAM Usage

Unfortunately, syncthing is unbelievably inefficient on most platforms such that is consumes a very large amount of CPU and RAM. Since RAM can be considered in most personal circumstances relatively cheap, the CPU consumption is relatively prohibitive, especially if you are running syncthing on highly optimised and minimal systems. For example, running syncthing (at version v0.11.25, at the time of writing) on an Macbook Air will keep your CPU constantly at about 20-30%. Since this is rather much, one can use cpulimit to forcibly allow syncthing to only use up an agreeable amount of CPU.

To use cpulimit, first install it via homebrew as you are used to:

brew install cpulimit

Assuming that syncthing is already installed, you will find the launcher in ~/Library/LaunchAgents/homebrew.mxcl.syncthing.plist.

First, change directory to the launch file:

cd ~/Library/LaunchAgents/

and stop syncthing by typing:

launchctl unload homebrew.mxcl.syncthing.plist

Next, edit homebrew.mxcl.syncthing.plist with your favourite editor to change some things. Find the subsection ProgramArguments:


and change it to this:



  • /usr/local/bin/cpulimit is the path to the cpulimit binary installed by homebrew.
  • –limit=5 means that only $5%$ CPU consumption is allowed at any time for syncthing and all child processes.

and the rest are default launch parameters for syncthing.

fuss/syncthing.txt · Last modified: 2017/02/22 18:30 (external edit)

Access website using Tor Access website using i2p

For the copyright, license, warranty and privacy terms for the usage of this website please see the license, privacy and plagiarism pages.