Synology Syncthing 2.0 doesn't start

Hi all,

for me its even working with v2.0.16 on a Synology 923+ with DSM 7.3.2-86009 Update 3.

Syncthing v2.0.16

syncthing

Package v2.0.14-34

syno_syncthing

br

A couple of days of use shown that both rc2 and 2.1 Release actually doesn’t work well on my Synology. I mean it’s not crashing as before, it starts and works a bit, but after couple of minutes strange things happen.

All remote devices disconnect, I am offline for them as well, synology resource monitor shows CPU and HDD loading from syncthing process but visually nothing happens in Syncthing. ST doesn’t respond to restart/shutdown commands. I tried to reinstall it completely but nothing helped until I installed v2.0.14-34.

Does anyone have similar problems?

Anything in the logs?

In the syncthing.log there are only connect/disconnect reports but there is another file panic-20260511-144921.reported.log that has thousands of suspicious strings.

This exact file has been saved right before I decided to replace rc2 to Release but it was already “broken” in a way I described above. I couldn’t update ST by usual upgrade button so I uninstalled rc2 and installed Release manually. Then it didn’t work, so I tried clean installation (uninstalled it with all the data) and now I don’t have any newer logs from Release version because I use v2.0.14-34.

If this log is not useless then I could spend some more time to install Release to get similar log file if it will help to fix the problem.

Here is the log file without IDs and IPs

panic-20260511-144921.reported.log (310.3 KB)

Hi there,

I have just updated my Syncthing from release 2.0.14-34 to 2.0.16-35 and it won’t start on my DS414 (7.1 armadaxp). Is there any way to roll back the version without losing all my settings? Can I help you understand what is not working by sharing logs? I don’t know where to get them, so I need directions for this

Same problem here with 2.0.16-35 on a DS214play.

The package has auto-upgraded itself and syncthing seems to stop immediately after being started manually. If there are any details or logs you’d like to see to help debug/fix just let me know!