I’m using the Docker container packaged by LinuxServer.io, but they don’t seem to be following up with any Beta releases. I can’t just switch to the official Syncthing version because of some possible conflicts between different image configurations. Maybe try contacting them.
Hi, I am running Syncthing on my Synology DS1821+ NAS which was installed using the SynoCummunity Installer.
I saw the shiny red button to upgrade to v2 at the top so pressed it and now Syncthing shows as running a process on the NAS but does not let me connect…
Is there a command a can possibly run on the NAS to reset or is my only option to uninstall and go back to v1 for now?
Also side question… Would all of my devices need to be upgraded to v2 to sync with each other or can v2 sync with v1?
Upgrading to V2 is a one-way, unstoppable process. You can try to wait for a while. If the problem still exists, it is recommended that you package the problematic configuration files, databases, etc. and send them to the developer for troubleshooting.
I am not sure whether the configuration files of V1 and V2 are compatible. If you cannot roll back to V1 directly, you can try to manually install V1 and then manually merge the configuration items in the V2 configuration file into the V1 configuration file. Obviously, this can reduce a lot of configuration work, but rescanning all files may take a long time.
Both versions can connect and sync with one another, i.e. there is no need to upgrade all devices to v2 in order to continue synchronising them.
They config files between the two versions use the same XML format and are compatible with each other.
1 Like
I just noticed an issue with my beta install
It shows that its actively syncing files but nothing is happening. and the folder on all systems shows that its fully synced.
Here are some screenshots I noticed this issue (was running beta8 at that point, upgraded to beta10 and the issue stayed) restarting the beta instance also has no effect.
I see no meaningful / any errors in the docker container logs. (all instances are docker containers v1.29.5)
this list took pretty long to populate ~10 seconds
instantly populated (note no pages)
if you need any other logs / files from me let me know.
I tested and the sync seems to still work. added a file on the source machine (1 machine has folder as send only, the others as receive only) and sync still works.
There was some database damage due to a bug in an earlier beta; if you ”touch” any of these files, do they sync? If not, I’m more interested and would like to look closer, can provide some database commands.
Just checked and it seems that all the files in the list are files that by now have been deleted. (expected behaviour off frigate (frigate is an NVR where I have auto-cleanup enabled) although the list shown in my previous post has grown in size (file-count and total size)
While checking though I noticed that the beta instance has more files that the source and the same for another normal instance.
folder settings
- source (send only)
- target (receive only)
- beta (receive only) “Ignore delete” is disabled on all these folders
I can’t disable the nvr for security reasons so there will still be changes in files. But I’m not touching anything Syncthing related in case you want me to try something specific.
screenshot for clarity.
Database backend switched from LevelDB to SQLite. These is a migration…
Should These be This ?
Yeah, bug from earlier beta, sorry. Reset database. 
or reset delta indexes everywhere.
No worries. That is why its called a beta.
I can confirm that resetting the database (only for that folder was enough) got everything back in sync.
Upgraded 2 devices to v2 so far, one went smooth the other one is stuck out of sync now for 7 out of 10 folders. The migration itself seemed to be successful.
no infos about why they are out if sync in the log or the gui, log just says
[4XXFU] 2025/04/22 13:22:11.280030 folder.go:438: INFO: Folder cloud isn't making sync progress - retrying in 8m17s. for the out of sync folders. GUI switches between “Preparing to Sync” and “Out of Sync” when it retries.
Another thing that seems weird is that syncthing sends >100MB to both remote devices that share most of the folders, this seems to repeat after every restart of syncthing.
What also seems wrong is that index-v0.14.0.db still existed with some files in it and after a restart. Syncthing v2 complained with the following lines and only started again after removing the old index folder.
[start] 2025/04/22 13:05:57.371173 utils.go:193: WARNING: Old-style database present but already migrated at 2025-04-22 12:13:06.858636008 +0200 CEST; please manually move or remove /home/alex/.config/syncthing/index-v0.14.0.db.
[start] 2025/04/22 13:06:02.379808 main.go:497: WARNING: Error opening database: openbase (PRAGMA journal_mode = WAL): database is locked
The following log file should contain one loop of trying to sync one of the folders that is stuck with “model” debug enabled: st-log.txt (5.1 KB)
I will leave it in this state for now so I can provide additional data if you need anything.
You can mimick SyncTrayzor with the Windows Task Scheduler. I have a task on my NAS that runs every hour and another task on my laptop that runs at log on and startup. There’s no tray icon, but this can be mimicked with a bookmark in whatever browser you use to the local ip of Syncthing. I’ve been running this configuration for years with little to no issues.
1 Like