Hi, I’m new to syncthing, yet very concerned on what I’ve experienced.
Syncthing is configured as follows:
- Running from docker compose (via portainer) with “network_mode: host” set as to eliminate any docker/host NAT issues
- Sync Protocol Listen Addresses at each device: tcp6://:22000
- All Discovery, NAT & Relay disabled
- Each device’s address specified as: tcp6://deviceX.domain.com:22000
In all regards, a direct connection between two devices.
On adding a folder and then accepting it a the destination device, files from device 1 (i.e. DSC0001.JPG) is created at device 2, yet only as tmp files (i.e. .syncthing.DSC0001.JPG.tmp)
The sync process simply doesn’t complete.
At the source device, the GUI states “Syncing (0%, 1.29 MiB)”, also reflecting the file as being out of sync.
At the destination device the GUI states “Syncing (14%, 1.1 Mib)” also reflecting the file as being out of sync.
… hours go by without any change …
Restarting, pausing et all other attempts has no effect.
And then the following shocker 
On scp’ing an image file to the source device’s folder, the filename is created, yet no content is transferred. On terminating the copy process, syncthing creates the file at the destination device, empty, and then syncs it back to the source device.
Now the question would be. Is it just a config issue on my side that can cause real damage or should there be a big warning put out to newcomers?
2 posts - 2 participants