|
|
@@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
|
|
|
.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
|
|
|
.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
|
|
|
..
|
|
|
-.TH "SYNCTHING-FAQ" "7" "Jul 09, 2024" "v1.27.7" "Syncthing"
|
|
|
+.TH "SYNCTHING-FAQ" "7" "Jul 18, 2024" "v1.27.7" "Syncthing"
|
|
|
.SH NAME
|
|
|
syncthing-faq \- Frequently Asked Questions
|
|
|
.INDENT 0.0
|
|
|
@@ -164,7 +164,7 @@ Directory modification times (not preserved)
|
|
|
Hard links (followed, not preserved)
|
|
|
.IP \(bu 2
|
|
|
Windows junctions (synced as ordinary directories; require enabling in
|
|
|
-\X'tty: link #config-option-folder.junctionsasdirs'\fI\%the configuration\fP\X'tty: link' on a per\-folder
|
|
|
+\fI\%the configuration\fP on a per\-folder
|
|
|
basis)
|
|
|
.IP \(bu 2
|
|
|
Resource forks (not preserved)
|
|
|
@@ -176,7 +176,7 @@ Devices, FIFOs, and other specials (ignored)
|
|
|
Sparse file sparseness (will become sparse, when supported by the OS & filesystem)
|
|
|
.IP \(bu 2
|
|
|
Syncthing internal files and folders (e.g. \fB\&.stfolder\fP, \fB\&.stignore\fP,
|
|
|
-\fB\&.stversions\fP, \X'tty: link #temporary-files'\fI\%temporary files\fP\X'tty: link', etc.)
|
|
|
+\fB\&.stversions\fP, \fI\%temporary files\fP, etc.)
|
|
|
.UNINDENT
|
|
|
.SS Is synchronization fast?
|
|
|
.sp
|
|
|
@@ -191,7 +191,7 @@ manner. This means that renaming a file will not cause a retransmission of
|
|
|
that file. Additionally, appending data to existing files should be handled
|
|
|
efficiently as well.
|
|
|
.sp
|
|
|
-\X'tty: link #temporary-files'\fI\%Temporary files\fP\X'tty: link' are used to store partial data
|
|
|
+\fI\%Temporary files\fP are used to store partial data
|
|
|
downloaded from other devices. They are automatically removed whenever a file
|
|
|
transfer has been completed or after the configured amount of time which is set
|
|
|
in the configuration file (24 hours by default).
|
|
|
@@ -236,7 +236,7 @@ oyster!)
|
|
|
\fBSEE ALSO:\fP
|
|
|
.INDENT 0.0
|
|
|
.INDENT 3.5
|
|
|
-\X'tty: link #device-ids'\fI\%Understanding Device IDs\fP\X'tty: link'
|
|
|
+\fI\%Understanding Device IDs\fP
|
|
|
.UNINDENT
|
|
|
.UNINDENT
|
|
|
.SH TROUBLESHOOTING
|
|
|
@@ -262,7 +262,7 @@ Devices” list on the right side of the GUI, double check that you see
|
|
|
.sp
|
|
|
If you are connected via a relay, this is because a direct connection could
|
|
|
not be established. Double check and follow the suggestions in
|
|
|
-\X'tty: link #firewall-setup'\fI\%Firewall Setup\fP\X'tty: link' to enable direct connections.
|
|
|
+\fI\%Firewall Setup\fP to enable direct connections.
|
|
|
.sp
|
|
|
Second, if one of the devices is a very low powered machine (a Raspberry Pi,
|
|
|
or a phone, or a NAS, or similar) you are likely constrained by the CPU on
|
|
|
@@ -295,8 +295,8 @@ causes a certain amount of extra CPU usage to calculate the summary data it
|
|
|
presents. Note however that once things are \fIin sync\fP CPU usage should be
|
|
|
negligible.
|
|
|
.sp
|
|
|
-To minimize the impact of this, Syncthing attempts to \X'tty: link #config-option-options.setlowpriority'\fI\%lower the
|
|
|
-process priority\fP\X'tty: link' when starting up.
|
|
|
+To minimize the impact of this, Syncthing attempts to \fI\%lower the
|
|
|
+process priority\fP when starting up.
|
|
|
.sp
|
|
|
To further limit the amount of CPU used when syncing and scanning, set the
|
|
|
environment variable \fBGOMAXPROCS\fP to the maximum number of CPU cores
|
|
|
@@ -328,7 +328,7 @@ protect against unauthorized access. Either:
|
|
|
.IP \(bu 2
|
|
|
Make sure the proxy sets a \fBHost\fP header containing \fBlocalhost\fP, or
|
|
|
.IP \(bu 2
|
|
|
-Set \X'tty: link #config-option-gui.insecureskiphostcheck'\fI\%gui.insecureSkipHostcheck\fP\X'tty: link' in the advanced settings, or
|
|
|
+Set \fI\%gui.insecureSkipHostcheck\fP in the advanced settings, or
|
|
|
.IP \(bu 2
|
|
|
Bind the GUI/API to a non\-localhost listen port.
|
|
|
.UNINDENT
|
|
|
@@ -338,8 +338,8 @@ In all cases, username/password authentication and HTTPS should be used.
|
|
|
.sp
|
|
|
This is almost always a result of bad RAM, storage device or other hardware.
|
|
|
When the index database is found to be corrupt Syncthing cannot operate and will
|
|
|
-note this in the logs and exit. To overcome this delete the \X'tty: link #config-locations'\fI\%database
|
|
|
-folder\fP\X'tty: link' inside Syncthing’s data directory and re\-start
|
|
|
+note this in the logs and exit. To overcome this delete the \fI\%database
|
|
|
+folder\fP inside Syncthing’s data directory and re\-start
|
|
|
Syncthing. It will then need to perform a full re\-hashing of all shared
|
|
|
folders. You should check your system in case the underlying cause is indeed
|
|
|
faulty hardware which may put the system at risk of further data loss.
|
|
|
@@ -374,7 +374,7 @@ up\-to\-date state with all the neighbours.
|
|
|
.SS Why does Syncthing connect to this unknown/suspicious address?
|
|
|
.sp
|
|
|
If you see outgoing connections to odd and unexpected addresses these are
|
|
|
-most likely connections to \X'tty: link #relaying'\fI\%relay servers\fP\X'tty: link'\&. Relay servers
|
|
|
+most likely connections to \fI\%relay servers\fP\&. Relay servers
|
|
|
are run by volunteers all over the world. They usually listen on ports 443 or
|
|
|
22067, though this is controlled by the user running it. You can compare the
|
|
|
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
|
|
|
@@ -420,7 +420,7 @@ Also see the \fI\%marker FAQ\fP for more information about the folder marker.
|
|
|
\fBSEE ALSO:\fP
|
|
|
.INDENT 0.0
|
|
|
.INDENT 3.5
|
|
|
-\X'tty: link #conflict-handling'\fI\%Conflicting Changes\fP\X'tty: link'
|
|
|
+\fI\%Conflicting Changes\fP
|
|
|
.UNINDENT
|
|
|
.UNINDENT
|
|
|
.SS How do I serve a folder from a read only filesystem?
|
|
|
@@ -682,7 +682,7 @@ echo 204800 | sudo tee /proc/sys/fs/inotify/max_user_watches
|
|
|
.SS How do I reset the GUI password?
|
|
|
.sp
|
|
|
If you’ve forgotten / lost the GUI password, you can reset it using the
|
|
|
-\X'tty: link #cmdoption-gui-password'\fI\%\-\-gui\-password\fP\X'tty: link' (and possibly \X'tty: link #cmdoption-gui-user'\fI\%\-\-gui\-user\fP\X'tty: link') options to the
|
|
|
+\fI\%\-\-gui\-password\fP (and possibly \fI\%\-\-gui\-user\fP) options to the
|
|
|
\fBsyncthing generate\fP subcommand. This should be done while Syncthing is not
|
|
|
running.
|
|
|
.INDENT 0.0
|
|
|
@@ -694,7 +694,7 @@ Stop Syncthing: \fBsyncthing cli operations shutdown\fP
|
|
|
Restart Syncthing as usual.
|
|
|
.UNINDENT
|
|
|
.sp
|
|
|
-\fIAlternatively, in step 2\fP, you can manually delete the \X'tty: link #config-option-gui.user'\fI\%<user>\fP\X'tty: link' and \X'tty: link #config-option-gui.password'\fI\%<password>\fP\X'tty: link' XML tags from the
|
|
|
+\fIAlternatively, in step 2\fP, you can manually delete the \fI\%<user>\fP and \fI\%<password>\fP XML tags from the
|
|
|
\fB<gui>\fP block in file \fBconfig.xml\fP\&. The location of the file depends on the
|
|
|
OS and is described in the \fI\%configuration documentation\fP\&.
|
|
|
.sp
|
Syncthing Release Automation