syncthing-faq.7 27 KB

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