syncthing-faq.7 33 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750
  1. .\" Man page generated from reStructuredText.
  2. .
  3. .
  4. .nr rst2man-indent-level 0
  5. .
  6. .de1 rstReportMargin
  7. \\$1 \\n[an-margin]
  8. level \\n[rst2man-indent-level]
  9. level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
  10. -
  11. \\n[rst2man-indent0]
  12. \\n[rst2man-indent1]
  13. \\n[rst2man-indent2]
  14. ..
  15. .de1 INDENT
  16. .\" .rstReportMargin pre:
  17. . RS \\$1
  18. . nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
  19. . nr rst2man-indent-level +1
  20. .\" .rstReportMargin post:
  21. ..
  22. .de UNINDENT
  23. . RE
  24. .\" indent \\n[an-margin]
  25. .\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
  26. .nr rst2man-indent-level -1
  27. .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
  28. .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
  29. ..
  30. .TH "SYNCTHING-FAQ" "7" "Sep 14, 2025" "v2.0.0" "Syncthing"
  31. .SH NAME
  32. syncthing-faq \- Frequently Asked Questions
  33. .INDENT 0.0
  34. .IP \(bu 2
  35. \fI\%General\fP
  36. .INDENT 2.0
  37. .IP \(bu 2
  38. \fI\%What is Syncthing?\fP
  39. .IP \(bu 2
  40. \fI\%Is it “syncthing”, “Syncthing” or “SyncThing”?\fP
  41. .IP \(bu 2
  42. \fI\%What things are synced?\fP
  43. .IP \(bu 2
  44. \fI\%Is synchronization fast?\fP
  45. .IP \(bu 2
  46. \fI\%How does Syncthing differ from BitTorrent/Resilio Sync?\fP
  47. .IP \(bu 2
  48. \fI\%Is there an iOS client?\fP
  49. .IP \(bu 2
  50. \fI\%Should I keep my device IDs secret?\fP
  51. .UNINDENT
  52. .IP \(bu 2
  53. \fI\%Troubleshooting\fP
  54. .INDENT 2.0
  55. .IP \(bu 2
  56. \fI\%Where are the Syncthing logs?\fP
  57. .IP \(bu 2
  58. \fI\%Why is the sync so slow?\fP
  59. .IP \(bu 2
  60. \fI\%Why does it use so much CPU?\fP
  61. .IP \(bu 2
  62. \fI\%Why is the setup more complicated than BitTorrent/Resilio Sync?\fP
  63. .IP \(bu 2
  64. \fI\%Why do I get “Host check error” in the GUI/API?\fP
  65. .IP \(bu 2
  66. \fI\%My Syncthing database is corrupt\fP
  67. .IP \(bu 2
  68. \fI\%Why do I see Syncthing twice in task manager?\fP
  69. .IP \(bu 2
  70. \fI\%How can I view the history of changes?\fP
  71. .IP \(bu 2
  72. \fI\%Does the audit log contain every change?\fP
  73. .IP \(bu 2
  74. \fI\%Why does Syncthing connect to this unknown/suspicious address?\fP
  75. .IP \(bu 2
  76. \fI\%I am seeing the error message “folder marker missing”. What do I do?\fP
  77. .IP \(bu 2
  78. \fI\%Why do my Windows computers always connect through a relay?\fP
  79. .UNINDENT
  80. .IP \(bu 2
  81. \fI\%Usage\fP
  82. .INDENT 2.0
  83. .IP \(bu 2
  84. \fI\%What if there is a conflict?\fP
  85. .IP \(bu 2
  86. \fI\%How do I serve a folder from a read only filesystem?\fP
  87. .IP \(bu 2
  88. \fI\%I really hate the .stfolder directory, can I remove it?\fP
  89. .IP \(bu 2
  90. \fI\%Am I able to nest shared folders in Syncthing?\fP
  91. .IP \(bu 2
  92. \fI\%How do I rename/move a synced folder?\fP
  93. .IP \(bu 2
  94. \fI\%How do I configure multiple users on a single machine?\fP
  95. .IP \(bu 2
  96. \fI\%Does Syncthing support syncing between folders on the same system?\fP
  97. .IP \(bu 2
  98. \fI\%When I do have two distinct Syncthing\-managed folders on two hosts, how does Syncthing handle moving files between them?\fP
  99. .IP \(bu 2
  100. \fI\%Can I help initial sync by copying files manually?\fP
  101. .IP \(bu 2
  102. \fI\%Is Syncthing my ideal backup application?\fP
  103. .IP \(bu 2
  104. \fI\%How can I exclude files with brackets ([]) in the name?\fP
  105. .IP \(bu 2
  106. \fI\%How do I access the web GUI from another computer?\fP
  107. .IP \(bu 2
  108. \fI\%I don’t like the GUI or the theme. Can it be changed?\fP
  109. .IP \(bu 2
  110. \fI\%How do I upgrade Syncthing?\fP
  111. .IP \(bu 2
  112. \fI\%Where do I find the latest release?\fP
  113. .IP \(bu 2
  114. \fI\%How do I run Syncthing as a daemon process on Linux?\fP
  115. .IP \(bu 2
  116. \fI\%How do I increase the inotify limit to get my filesystem watcher to work?\fP
  117. .IP \(bu 2
  118. \fI\%How do I reset the GUI password?\fP
  119. .UNINDENT
  120. .UNINDENT
  121. .SH GENERAL
  122. .SS What is Syncthing?
  123. .sp
  124. Syncthing is an application that lets you synchronize your files across multiple
  125. devices. This means the creation, modification or deletion of files on one
  126. machine will automatically be replicated to your other devices. We believe your
  127. data is your data alone and you deserve to choose where it is stored. Therefore
  128. Syncthing does not upload your data to the cloud but exchanges your data across
  129. your machines as soon as they are online at the same time.
  130. .SS Is it “syncthing”, “Syncthing” or “SyncThing”?
  131. .sp
  132. It’s \fBSyncthing\fP, although the command and source repository is spelled
  133. \fBsyncthing\fP so it may be referred to in that way as well. It’s definitely not
  134. SyncThing, even though the abbreviation \fBst\fP is used in some
  135. circumstances and file names.
  136. .SS What things are synced?
  137. .sp
  138. The following things are \fIalways\fP synchronized:
  139. .INDENT 0.0
  140. .IP \(bu 2
  141. File contents
  142. .IP \(bu 2
  143. File modification times
  144. .UNINDENT
  145. .sp
  146. The following may be synchronized or not, depending:
  147. .INDENT 0.0
  148. .IP \(bu 2
  149. File permissions (when supported by file system; on Windows only the
  150. read only bit is synchronized)
  151. .IP \(bu 2
  152. Symbolic links (synced, except on Windows, but never followed)
  153. .IP \(bu 2
  154. File or directory owners and groups (when enabled)
  155. .IP \(bu 2
  156. Extended attributes (when enabled)
  157. .IP \(bu 2
  158. POSIX or NFS ACLs (as part of extended attributes)
  159. .UNINDENT
  160. .sp
  161. \fBNOTE:\fP
  162. .INDENT 0.0
  163. .INDENT 3.5
  164. Note that what can be synced often depends on the operating system, file
  165. system, and possibly other factors. For example, even though Syncthing may
  166. try to synchronise symbolic links on Android, this will not succeed, as the
  167. OS does not support them on the user storage.
  168. .UNINDENT
  169. .UNINDENT
  170. .sp
  171. The following are \fInot\fP synchronized;
  172. .INDENT 0.0
  173. .IP \(bu 2
  174. Directory modification times (not preserved)
  175. .IP \(bu 2
  176. Hard links (followed, not preserved)
  177. .IP \(bu 2
  178. Windows junctions (synced as ordinary directories; require enabling in
  179. \fI\%the configuration\fP on a per\-folder
  180. basis)
  181. .IP \(bu 2
  182. Resource forks (not preserved)
  183. .IP \(bu 2
  184. Windows ACLs (not preserved)
  185. .IP \(bu 2
  186. Devices, FIFOs, and other specials (ignored)
  187. .IP \(bu 2
  188. Sparse file sparseness (will become sparse, when supported by the OS & filesystem)
  189. .IP \(bu 2
  190. Syncthing internal files and folders (e.g. \fB\&.stfolder\fP, \fB\&.stignore\fP,
  191. \fB\&.stversions\fP, \fI\%temporary files\fP, etc.)
  192. .UNINDENT
  193. .SS Is synchronization fast?
  194. .sp
  195. Syncthing segments files into pieces, called blocks, to transfer data from one
  196. device to another. Therefore, multiple devices can share the synchronization
  197. load, in a similar way to the torrent protocol. The more devices you have online,
  198. the faster an additional device will receive the data
  199. because small blocks will be fetched from all devices in parallel.
  200. .sp
  201. Syncthing handles renaming files and updating their metadata in an efficient
  202. manner. This means that renaming a file will not cause a retransmission of
  203. that file. Additionally, appending data to existing files should be handled
  204. efficiently as well.
  205. .sp
  206. \fI\%Temporary files\fP are used to store partial data
  207. downloaded from other devices. They are automatically removed whenever a file
  208. transfer has been completed or after the configured amount of time which is set
  209. in the configuration file (24 hours by default).
  210. .SS How does Syncthing differ from BitTorrent/Resilio Sync?
  211. .sp
  212. The two are different and not related. Syncthing and BitTorrent/Resilio Sync accomplish
  213. some of the same things, namely syncing files between two or more computers.
  214. .sp
  215. BitTorrent Sync, now called Resilio Sync, is a proprietary peer\-to\-peer file
  216. synchronization tool available for Windows, Mac, Linux, Android, iOS, Windows
  217. Phone, Amazon Kindle Fire and BSD. [1] Syncthing is an open source file
  218. synchronization tool.
  219. .sp
  220. Syncthing uses an open and documented protocol, and likewise the security
  221. mechanisms in use are well defined and visible in the source code. Resilio
  222. Sync uses an undocumented, closed protocol with unknown security properties.
  223. .IP [1] 5
  224. \X'tty: link https://en.wikipedia.org/wiki/Resilio_Sync'\fI\%https://en.wikipedia.org/wiki/Resilio_Sync\fP\X'tty: link'
  225. .SS Is there an iOS client?
  226. .sp
  227. There are no plans by the current Syncthing team to officially support iOS in the foreseeable future.
  228. .sp
  229. iOS has significant restrictions on background processing that make it very hard to
  230. run Syncthing reliably and integrate it into the system.
  231. .sp
  232. However, there is an open source app for iOS, incorporating Syncthing, that attempts to work within
  233. these limitations. It provides a native UI and features for selective synchronization as well as
  234. on\-demand access to files. Most Syncthing features are available, but the native UI is simplified
  235. compared to the official client. [2]
  236. .sp
  237. There is also a commercial packaging of Syncthing. It provides access to all Syncthing functionalities
  238. through the original UI. [3]
  239. .IP [2] 5
  240. \X'tty: link https://github.com/pixelspark/sushitrain'\fI\%https://github.com/pixelspark/sushitrain\fP\X'tty: link'
  241. .IP [3] 5
  242. \X'tty: link https://www.mobiussync.com'\fI\%https://www.mobiussync.com\fP\X'tty: link'
  243. .SS Should I keep my device IDs secret?
  244. .sp
  245. No. The IDs are not sensitive. Given a device ID it’s possible to find the IP
  246. address for that device, if global discovery is enabled on it. Knowing the device
  247. ID doesn’t help you actually establish a connection to that device or get a list
  248. of files, etc.
  249. .sp
  250. For a connection to be established, both devices need to know about the other’s
  251. device ID. It’s not possible (in practice) to forge a device ID. (To forge a
  252. device ID you need to create a TLS certificate with that specific SHA\-256 hash.
  253. If you can do that, you can spoof any TLS certificate. The world is your
  254. oyster!)
  255. .sp
  256. \fBSEE ALSO:\fP
  257. .INDENT 0.0
  258. .INDENT 3.5
  259. \fI\%Understanding Device IDs\fP
  260. .UNINDENT
  261. .UNINDENT
  262. .SH TROUBLESHOOTING
  263. .SS Where are the Syncthing logs?
  264. .sp
  265. Syncthing logs to stdout by default. On Windows Syncthing by default also
  266. creates \fBsyncthing.log\fP in Syncthing’s home directory (run \fBsyncthing
  267. \-\-paths\fP to see where that is). The command line option \fB\-\-logfile\fP can be
  268. used to specify a user\-defined logfile. If you only have access to a running
  269. instance’s GUI, click the \fIHelp\fP \-> \fIAbout\fP menu item, then the \fIPaths\fP tab.
  270. .sp
  271. If you’re running a process manager like systemd, check there. If you’re
  272. using a GUI wrapper integration, it may keep the logs for you.
  273. .SS Why is the sync so slow?
  274. .sp
  275. When troubleshooting a slow sync, there are a number of things to check.
  276. .sp
  277. First of all, verify that you are not connected via a relay. In the “Remote
  278. Devices” list on the right side of the GUI, double check that the Connection
  279. Type does \fInot\fP start with “Relay”.
  280. .sp
  281. Here is an example of a device connected via a relay:
  282. [image]
  283. .sp
  284. If you are connected via a relay, this is because a direct connection could
  285. not be established. Double check and follow the suggestions in
  286. \fI\%Firewall Setup\fP to enable direct connections.
  287. .sp
  288. Second, if one of the devices is a very low powered machine (a Raspberry Pi,
  289. or a phone, or a NAS, or similar) you are likely constrained by the CPU on
  290. that device. See the next question for reasons Syncthing likes a faster CPU.
  291. .sp
  292. Third, verify that the network connection is OK. Tools such as iperf or just
  293. an Internet speed test can be used to verify the performance here.
  294. .SS Why does it use so much CPU?
  295. .INDENT 0.0
  296. .IP 1. 3
  297. When new or changed files are detected, or Syncthing starts for the
  298. first time, your files are hashed using SHA\-256.
  299. .IP 2. 3
  300. Data that is sent over the network is compressed (optionally) and
  301. encrypted (always). When receiving data it must be decrypted and then (if
  302. compressed) decompressed.
  303. .IP 3. 3
  304. There is a certain amount of housekeeping that must be done to track the
  305. current and available versions of each file in the index database.
  306. .IP 4. 3
  307. By default Syncthing uses periodic scanning every hour when watching for
  308. changes or every minute if that’s disabled to detect
  309. file changes. This means checking every file’s modification time and
  310. comparing it to the database. This can cause spikes of CPU usage for large
  311. folders.
  312. .UNINDENT
  313. .sp
  314. Hashing, compression and encryption cost CPU time. Also, using the GUI
  315. causes a certain amount of extra CPU usage to calculate the summary data it
  316. presents. Note however that once things are \fIin sync\fP CPU usage should be
  317. negligible.
  318. .sp
  319. To minimize the impact of this, Syncthing attempts to \fI\%lower the
  320. process priority\fP when starting up.
  321. .sp
  322. To further limit the amount of CPU used when syncing and scanning, set the
  323. environment variable \fBGOMAXPROCS\fP to the maximum number of CPU cores
  324. Syncthing should use at any given moment. For example, \fBGOMAXPROCS=2\fP on a
  325. machine with four cores will limit Syncthing to no more than half the
  326. system’s CPU power.
  327. .SS Why is the setup more complicated than BitTorrent/Resilio Sync?
  328. .sp
  329. Security over convenience. In Syncthing you have to set up both sides to
  330. connect two devices. An attacker can’t do much with a stolen device ID, because
  331. you have to add the device on the other side too. You have better control
  332. where your files are transferred.
  333. .sp
  334. This is an area that we are working to improve in the long term.
  335. .SS Why do I get “Host check error” in the GUI/API?
  336. .sp
  337. Since version 0.14.6 Syncthing does an extra security check when the GUI/API
  338. is bound to localhost \- namely that the browser is talking to localhost.
  339. This protects against most forms of \X'tty: link https://en.wikipedia.org/wiki/DNS_rebinding'\fI\%DNS rebinding attack\fP <\fBhttps://en.wikipedia.org/wiki/DNS_rebinding\fP>\X'tty: link' against the GUI.
  340. .sp
  341. To pass this test, ensure that you are accessing the GUI using an URL that
  342. begins with \fBhttp://localhost\fP, \fBhttp://127.0.0.1\fP or \fBhttp://[::1]\fP\&. HTTPS
  343. is fine too, of course.
  344. .sp
  345. If you are using a proxy in front of Syncthing you may need to disable this
  346. check, after ensuring that the proxy provides sufficient authentication to
  347. protect against unauthorized access. Either:
  348. .INDENT 0.0
  349. .IP \(bu 2
  350. Make sure the proxy sets a \fBHost\fP header containing \fBlocalhost\fP, or
  351. .IP \(bu 2
  352. Set \fI\%gui.insecureSkipHostcheck\fP in the advanced settings, or
  353. .IP \(bu 2
  354. Bind the GUI/API to a non\-localhost listen port.
  355. .UNINDENT
  356. .sp
  357. In all cases, username/password authentication and HTTPS should be used.
  358. .SS My Syncthing database is corrupt
  359. .sp
  360. This is almost always a result of bad RAM, storage device or other hardware.
  361. When the index database is found to be corrupt Syncthing cannot operate and will
  362. note this in the logs and exit. To overcome this delete the \fI\%database
  363. folder\fP inside Syncthing’s data directory and re\-start
  364. Syncthing. It will then need to perform a full re\-hashing of all shared
  365. folders. You should check your system in case the underlying cause is indeed
  366. faulty hardware which may put the system at risk of further data loss.
  367. .SS Why do I see Syncthing twice in task manager?
  368. .sp
  369. One process manages the other, to capture logs and manage restarts. This
  370. makes it easier to handle upgrades from within Syncthing itself, and also
  371. ensures that we get a nice log file to help us narrow down the cause for
  372. crashes and other bugs.
  373. .SS How can I view the history of changes?
  374. .sp
  375. The web GUI contains a \fBRecent Changes\fP button under the device list which
  376. displays changes since the last (re)start of Syncthing. With the \fB\-\-audit\fP
  377. option you can enable a persistent, detailed log of changes and most
  378. activities, which contains a JSON\-formatted sequence of events in the
  379. \fB~/.local/state/syncthing/audit\-_date_\-_time_.log\fP file.
  380. .SS Does the audit log contain every change?
  381. .sp
  382. The audit log (and the \fBRecent Changes\fP window) sees the changes that your
  383. Syncthing sees. When Syncthing is continuously connected it usually sees every change
  384. happening immediately and thus knows which node initiated the change.
  385. When topology gets complex or when your node reconnects after some time offline,
  386. Syncthing synchronises with its neighbours: It gets the latest synchronised state
  387. from the neighbour, which is the \fIresult\fP of all the changes between the last
  388. known state (before disconnect or network delay) and the current state at the
  389. neighbour, and if there were updates, deletes, creates, conflicts, which were
  390. overlapping we only see the \fIlatest change\fP for a given file or directory (and
  391. the node where that latest change occurred). When we connect to multiple neighbours
  392. Syncthing decides which neighbour has the latest state, or if the states conflict
  393. it initiates the conflict resolution procedure, which in the end results in a consistent
  394. up\-to\-date state with all the neighbours.
  395. .SS Why does Syncthing connect to this unknown/suspicious address?
  396. .sp
  397. If you see outgoing connections to odd and unexpected addresses these are
  398. most likely connections to \fI\%relay servers\fP\&. Relay servers
  399. are run by volunteers all over the world. They usually listen on ports 443 or
  400. 22067, though this is controlled by the user running it. You can compare the
  401. address you are concerned about with \X'tty: link https://relays.syncthing.net'\fI\%the current list of active relays\fP <\fBhttps://relays.syncthing.net\fP>\X'tty: link'\&. Relays do not and can not see the data
  402. transmitted via them.
  403. .SS I am seeing the error message “folder marker missing”. What do I do?
  404. .sp
  405. Syncthing uses a specific marker usually called \fB\&.stfolder\fP to determine whether
  406. a folder is healthy. This is a safety check to ensure that your folder is properly
  407. readable and present on disk. For example, if you remove a USB drive from your computer
  408. or unmount a filesystem, then syncthing must know whether you have really deleted \fBall\fP of
  409. your files. Therefore, syncthing always checks that the \fB\&.stfolder\fP is present.
  410. .sp
  411. When this error appears, syncthing assumes that the folder has encountered some type of error
  412. and will stop syncing it until the \fB\&.stfolder\fP reappears. Once that happens, all changes made
  413. to the folder locally will be synced (i.e. missing files will be considered deletions).
  414. .INDENT 0.0
  415. .IP \(bu 2
  416. If you get this error message, check the folder in question on your storage. If you have
  417. unmounted the folder (or a parent of it), you must remount it for syncthing to resume syncing
  418. this folder.
  419. .IP \(bu 2
  420. If you have moved the folder, you must either move it back to its original location, or remove the
  421. folder from within the syncthing UI and re\-add it at its new location.
  422. .IP \(bu 2
  423. If the folder is present on disk, with all of its children files and directories, but the \fB\&.stfolder\fP
  424. is still missing:
  425. .sp
  426. It is possible that a file cleaning software has removed the \fB\&.stfolder\fP\&. Some software
  427. removes empty folders, and the \fB\&.stfolder\fP is often empty. This happens particularly often on Android.
  428. To remediate, recreate the \fB\&.stfolder\fP and add a dummy file in it, or add an exception to your
  429. cleaning software.
  430. .UNINDENT
  431. .sp
  432. If you are still unsure what has happened, you can remove the folder from within the syncthing UI and re\-add it
  433. at the same location. This causes syncthing to attempt an automatic re\-creation of the \fB\&.stfolder\fP\&. Next,
  434. it will also reset the database state of this folder. It will be considered a “new” folder, meaning that its files
  435. will be merged with files from remote devices.
  436. .sp
  437. Also see the \fI\%marker FAQ\fP for more information about the folder marker.
  438. .SS Why do my Windows computers always connect through a relay?
  439. .sp
  440. When connecting to a new network, Windows by default sets its profile to
  441. “Public”. While being more secure, this setting commonly prevents applications
  442. like Syncthing from being able to establish direct connections with the device
  443. in question, forcing it to connect through a relay. If you would rather connect
  444. your devices directly, please follow \X'tty: link https://support.microsoft.com/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9#bkmk_network_profile'\fI\%the official Microsoft instructions on how
  445. to change the network profile to “Private”\fP <\fBhttps://support.microsoft.com/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9#bkmk_network_profile\fP>\X'tty: link'\&.
  446. .SH USAGE
  447. .SS What if there is a conflict?
  448. .sp
  449. \fBSEE ALSO:\fP
  450. .INDENT 0.0
  451. .INDENT 3.5
  452. \fI\%Conflicting Changes\fP
  453. .UNINDENT
  454. .UNINDENT
  455. .SS How do I serve a folder from a read only filesystem?
  456. .sp
  457. Syncthing requires a “folder marker” to indicate that the folder is present
  458. and healthy. By default this is a directory called \fB\&.stfolder\fP that is
  459. created by Syncthing when the folder is added. If this folder can’t be
  460. created (you are serving files from a CD or something) you can instead set
  461. the advanced config \fBMarker Name\fP to the name of some file or folder that
  462. you know will always exist in the folder.
  463. .SS I really hate the \fB\&.stfolder\fP directory, can I remove it?
  464. .sp
  465. See the previous question.
  466. .SS Am I able to nest shared folders in Syncthing?
  467. .sp
  468. Sharing a folder that is within an already shared folder is possible, but it has
  469. its caveats. What you must absolutely avoid are circular shares. This is just
  470. one example, there may be other undesired effects. Nesting shared folders is not
  471. supported, recommended or coded for, but it can be done successfully when you
  472. know what you’re doing \- you have been warned.
  473. .SS How do I rename/move a synced folder?
  474. .sp
  475. Syncthing doesn’t have a direct way to do this, as it’s potentially
  476. dangerous to do so if you’re not careful \- it may result in data loss if
  477. something goes wrong during the move and is synchronized to your other
  478. devices.
  479. .sp
  480. The easy way to rename or move a synced folder on the local system is to
  481. remove the folder in the Syncthing UI, move it on disk, then re\-add it using
  482. the new path.
  483. .sp
  484. It’s important to do this when the folder is already in sync between your
  485. devices, as it is otherwise unpredictable which changes will “win” after the
  486. move. Changes made on other devices may be overwritten, or changes made
  487. locally may be overwritten by those on other devices.
  488. .sp
  489. An alternative way is to shut down Syncthing, move the folder on disk (including
  490. the \fB\&.stfolder\fP marker), edit the path directly in \fBconfig.xml\fP in the
  491. configuration folder (see \fI\%Syncthing Configuration\fP) and then start Syncthing again.
  492. .SS How do I configure multiple users on a single machine?
  493. .sp
  494. Each user should run their own Syncthing instance. Be aware that you might need
  495. to configure listening ports such that they do not overlap (see \fI\%Syncthing Configuration\fP).
  496. .SS Does Syncthing support syncing between folders on the same system?
  497. .sp
  498. No. Syncthing is not designed to sync locally and the overhead involved in
  499. doing so using Syncthing’s method would be wasteful. There are better
  500. programs to achieve this such as \X'tty: link https://rsync.samba.org/'\fI\%rsync\fP <\fBhttps://rsync.samba.org/\fP>\X'tty: link' or
  501. \X'tty: link https://www.cis.upenn.edu/~bcpierce/unison'\fI\%Unison\fP <\fBhttps://www.cis.upenn.edu/~bcpierce/unison\fP>\X'tty: link'\&.
  502. .SS When I do have two distinct Syncthing\-managed folders on two hosts, how does Syncthing handle moving files between them?
  503. .sp
  504. Syncthing does not specially handle this case, and most files will most likely get
  505. re\-downloaded.
  506. .sp
  507. In detail, the behavior depends on the scan order. If you have folders A and B,
  508. and move files from A to B, if A gets scanned first, it will announce the removal of
  509. the files to others who will then remove the files. As you rescan B, B will
  510. announce the addition of new files, and other peers will have nowhere to get
  511. them from apart from re\-downloading them.
  512. .sp
  513. If B gets rescanned first, B will announce additions first, and remote
  514. peers will then reconstruct the files (not rename, more like copying block by
  515. block) from A, and then as A gets rescanned, it will remove the files from A.
  516. .sp
  517. A workaround would be to copy first from A to B, rescan B, wait for B to
  518. copy the files on the remote side, and then delete from A.
  519. .SS Can I help initial sync by copying files manually?
  520. .sp
  521. If you have a large folder that you want to keep in sync over a not\-so\-fast network, and you have the possibility to move all files to the remote device in a faster manner, here is a procedure to follow:
  522. .INDENT 0.0
  523. .IP \(bu 2
  524. Create the folder on the local device, but don’t share it with the remote device yet.
  525. .IP \(bu 2
  526. Copy the files from the local device to the remote device using regular file copy. If this takes a long time (perhaps requiring travelling there physically), it may be a good idea to make sure that the files on the local device are not updated while you are doing this.
  527. .IP \(bu 2
  528. Create the folder on the remote device, and copy the Folder ID from the folder on the local device, as we want the folders to be considered the same. Then wait until scanning the folder is done.
  529. .IP \(bu 2
  530. Now share the folder with the other device, on both sides. Syncthing will exchange file information, updating the database, but existing files will not be transferred. This may still take a while initially, be patient and wait until it settled.
  531. .UNINDENT
  532. .SS Is Syncthing my ideal backup application?
  533. .sp
  534. No. Syncthing is not a great backup application because all changes to your
  535. files (modifications, deletions, etc.) will be propagated to all your
  536. devices. You can enable versioning, but we encourage you to use other tools
  537. to keep your data safe from your (or our) mistakes.
  538. .SS How can I exclude files with brackets (\fB[]\fP) in the name?
  539. .sp
  540. The patterns in .stignore are glob patterns, where brackets are used to
  541. denote character ranges. That is, the pattern \fBq[abc]x\fP will match the
  542. files \fBqax\fP, \fBqbx\fP and \fBqcx\fP\&.
  543. .sp
  544. To match an actual file \fIcalled\fP \fBq[abc]x\fP the pattern needs to “escape”
  545. the brackets, like so: \fBq\e[abc\e]x\fP\&.
  546. .sp
  547. On Windows, use the \fB|\fP character to escape the brackets (\fBq|[abc|]x\fP), as the \fB\e\fP
  548. character is used as a path separator.
  549. .SS How do I access the web GUI from another computer?
  550. .sp
  551. The default listening address is 127.0.0.1:8384, so you can only access the GUI
  552. from the same machine. This is for security reasons. To access it from another
  553. computer, change the \fBGUI listen address\fP option in the web GUI from
  554. \fB127.0.0.1:8384\fP to \fB0.0.0.0:8384\fP, or change the \fBconfig.xml\fP:
  555. .INDENT 0.0
  556. .INDENT 3.5
  557. .sp
  558. .EX
  559. <gui enabled=\(dqtrue\(dq tls=\(dqfalse\(dq>
  560. <address>127.0.0.1:8384</address>
  561. .EE
  562. .UNINDENT
  563. .UNINDENT
  564. .sp
  565. to
  566. .INDENT 0.0
  567. .INDENT 3.5
  568. .sp
  569. .EX
  570. <gui enabled=\(dqtrue\(dq tls=\(dqtrue\(dq>
  571. <address>0.0.0.0:8384</address>
  572. .EE
  573. .UNINDENT
  574. .UNINDENT
  575. .sp
  576. Then the GUI is accessible from everywhere. There is no filtering based on
  577. e.g. source address (use a firewall for that). You should set a password and
  578. enable HTTPS with this configuration. You can do this from inside the GUI.
  579. .sp
  580. If both your computers are Unix\-like (Linux, Mac, etc.) you can also leave the
  581. GUI settings at default and use an SSH port forward to access it. For example,
  582. .INDENT 0.0
  583. .INDENT 3.5
  584. .sp
  585. .EX
  586. $ ssh \-L 9090:127.0.0.1:8384 [email protected]
  587. .EE
  588. .UNINDENT
  589. .UNINDENT
  590. .sp
  591. will log you into \fBothercomputer.example.com\fP, and present the \fIremote\fP
  592. Syncthing GUI on \X'tty: link http://localhost:9090'\fI\%http://localhost:9090\fP\X'tty: link' on your \fIlocal\fP computer.
  593. .sp
  594. If you only want to access the remote GUI and don’t want the terminal session,
  595. use this example:
  596. .INDENT 0.0
  597. .INDENT 3.5
  598. .sp
  599. .EX
  600. $ ssh \-N \-L 9090:127.0.0.1:8384 [email protected]
  601. .EE
  602. .UNINDENT
  603. .UNINDENT
  604. .sp
  605. If only your remote computer is Unix\-like, you can still access it with SSH from
  606. Windows. Under Windows 10 or later you can use the same \fBssh\fP command if you
  607. \X'tty: link https://learn.microsoft.com/windows-server/administration/openssh/openssh_install_firstuse'\fI\%install the OpenSSH Client\fP <\fBhttps://learn.microsoft.com/windows-server/administration/openssh/openssh_install_firstuse\fP>\X'tty: link'\&.
  608. .SS I don’t like the GUI or the theme. Can it be changed?
  609. .sp
  610. You can change the theme in the settings. Syncthing ships with other themes
  611. than the default.
  612. .sp
  613. If you want a custom theme or a completely different GUI, you can add your
  614. own.
  615. By default, Syncthing will look for a directory \fBgui\fP inside the Syncthing
  616. home folder. To change the directory to look for themes, you need to set the
  617. STGUIASSETS environment variable. To get the concrete directory, run
  618. syncthing with the \fB\-\-paths\fP parameter. It will print all the relevant paths,
  619. including the “GUI override directory”.
  620. .sp
  621. To add e.g. a red theme, you can create the file \fBred/assets/css/theme.css\fP
  622. inside the GUI override directory to override the default CSS styles.
  623. .sp
  624. To create a whole new GUI, you should checkout the files at
  625. \X'tty: link https://github.com/syncthing/syncthing/tree/main/gui/default'\fI\%https://github.com/syncthing/syncthing/tree/main/gui/default\fP\X'tty: link'
  626. to get an idea how to do that.
  627. .SS How do I upgrade Syncthing?
  628. .sp
  629. If you use a package manager such as Debian’s apt\-get, you should upgrade
  630. using the package manager. If you use the binary packages linked from
  631. Syncthing.net, you can use Syncthing’s built\-in automatic upgrade functionality.
  632. .INDENT 0.0
  633. .IP \(bu 2
  634. If automatic upgrades is enabled (which is the default), Syncthing will
  635. upgrade itself automatically within 24 hours of a new release.
  636. .IP \(bu 2
  637. The upgrade button appears in the web GUI when a new version has been
  638. released. Pressing it will perform an upgrade.
  639. .IP \(bu 2
  640. To force an upgrade from the command line, run \fBsyncthing \-\-upgrade\fP\&.
  641. .UNINDENT
  642. .sp
  643. Note that your system should have CA certificates installed which allows a
  644. secure connection to GitHub (e.g. FreeBSD requires \fBsudo pkg install
  645. ca_root_nss\fP). If \fBcurl\fP or \fBwget\fP works with normal HTTPS sites, then
  646. so should Syncthing.
  647. .SS Where do I find the latest release?
  648. .sp
  649. We release new versions through GitHub. The latest release is always found
  650. \X'tty: link https://github.com/syncthing/syncthing/releases/latest'\fI\%on the release page\fP <\fBhttps://github.com/syncthing/syncthing/releases/latest\fP>\X'tty: link'\&. Unfortunately
  651. GitHub does not provide a single URL to automatically download the latest
  652. version. We suggest to use the \X'tty: link https://api.github.com/repos/syncthing/syncthing/releases/latest'\fI\%GitHub API\fP <\fBhttps://api.github.com/repos/syncthing/syncthing/releases/latest\fP>\X'tty: link' and parsing
  653. the JSON response.
  654. .SS How do I run Syncthing as a daemon process on Linux?
  655. .sp
  656. If you’re using systemd, runit, or upstart, we ship \X'tty: link https://github.com/syncthing/syncthing/tree/main/etc'\fI\%example configurations\fP <\fBhttps://github.com/syncthing/syncthing/tree/main/etc\fP>\X'tty: link'\&.
  657. .sp
  658. If however you’re not using one of these tools, you have a couple of options.
  659. If your system has a tool called \fBstart\-stop\-daemon\fP installed (that’s the name
  660. of the command, not the package), look into the local documentation for that, it
  661. will almost certainly cover 100% of what you want to do. If you don’t have
  662. \fBstart\-stop\-daemon\fP, there are a bunch of other software packages you could use
  663. to do this. The most well known is called daemontools, and can be found in the
  664. standard package repositories for almost every modern Linux distribution.
  665. Other popular tools with similar functionality include S6 and the aforementioned
  666. runit.
  667. .SS How do I increase the inotify limit to get my filesystem watcher to work?
  668. .sp
  669. You are probably reading this because you encountered the following error with
  670. the filesystem watcher on linux:
  671. .INDENT 0.0
  672. .INDENT 3.5
  673. Failed to start filesystem watcher for folder yourLabel (yourID): failed to
  674. set up inotify handler. Please increase inotify limits, see \X'tty: link https://docs.syncthing.net/users/faq.html#inotify-limits'\fI\%https://docs.syncthing.net/users/faq.html#inotify\-limits\fP\X'tty: link'
  675. .UNINDENT
  676. .UNINDENT
  677. .sp
  678. Linux typically restricts the number of watches per user (usually 8192). If
  679. you have many directories, you will need to adjust that number.
  680. .sp
  681. On many Linux distributions you can run the following to fix it:
  682. .INDENT 0.0
  683. .INDENT 3.5
  684. .sp
  685. .EX
  686. echo \(dqfs.inotify.max_user_watches=204800\(dq | sudo tee \-a /etc/sysctl.conf
  687. .EE
  688. .UNINDENT
  689. .UNINDENT
  690. .sp
  691. On Arch Linux and potentially others it is preferred to write this line into a
  692. separate file, i.e. you should run:
  693. .INDENT 0.0
  694. .INDENT 3.5
  695. .sp
  696. .EX
  697. echo \(dqfs.inotify.max_user_watches=204800\(dq | sudo tee \-a /etc/sysctl.d/90\-override.conf
  698. .EE
  699. .UNINDENT
  700. .UNINDENT
  701. .sp
  702. This only takes effect after a reboot. To adjust the limit immediately, run:
  703. .INDENT 0.0
  704. .INDENT 3.5
  705. .sp
  706. .EX
  707. echo 204800 | sudo tee /proc/sys/fs/inotify/max_user_watches
  708. .EE
  709. .UNINDENT
  710. .UNINDENT
  711. .SS How do I reset the GUI password?
  712. .sp
  713. If you’ve forgotten / lost the GUI password, you can reset it using the
  714. \fI\%\-\-gui\-password\fP (and possibly \fI\%\-\-gui\-user\fP) options to the
  715. \fBsyncthing generate\fP subcommand. This should be done while Syncthing is not
  716. running.
  717. .INDENT 0.0
  718. .IP 1. 3
  719. Stop Syncthing: \fBsyncthing cli operations shutdown\fP
  720. .IP 2. 3
  721. \fBsyncthing generate \-\-gui\-password=myNewPassword \-\-gui\-user=newUserName\fP
  722. .IP 3. 3
  723. Restart Syncthing as usual.
  724. .UNINDENT
  725. .sp
  726. \fIAlternatively, in step 2\fP, you can manually delete the \fI\%<user>\fP and \fI\%<password>\fP XML tags from the
  727. \fB<gui>\fP block in file \fBconfig.xml\fP\&. The location of the file depends on the
  728. OS and is described in the \fI\%configuration documentation\fP\&.
  729. .sp
  730. For example, the two emphasized lines below would be removed from the file.
  731. .INDENT 0.0
  732. .INDENT 3.5
  733. .sp
  734. .EX
  735. <gui enabled=\(dqtrue\(dq tls=\(dqfalse\(dq>
  736. <address>127.0.0.1:8384</address>
  737. <user>syncguy</user>
  738. <password>$2a$10$s9wWHOQe...Cq7GPye69</password>
  739. <apikey>9RCKohqCAyrj5RjpyZdR2wXmQ9PyQFeN</apikey>
  740. <theme>default</theme>
  741. </gui>
  742. .EE
  743. .UNINDENT
  744. .UNINDENT
  745. .SH AUTHOR
  746. The Syncthing Authors
  747. .SH COPYRIGHT
  748. 2014-2025, The Syncthing Authors
  749. .\" Generated by docutils manpage writer.
  750. .