syncthing-faq.7 32 KB

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