Updated both my server and my windows app but sync is not working

[Ghofran566]

Hey and thanks to all of contributers of this project
I have updated both my server (Ubuntu 22.02 + Docker) and also my windows app
both are version 0.106.1 but now when i want to sync my notes from the windows app i get:
"Sync failed: Could not setup sync since local sync protocol version is 39 while remote is 41. To fix this issue, use same Trilium version on all instances."
How could i fix this issue?

[dgesteves]

Your Windows app is the real 0.106.1. The server isn't. Every release from 0.103.0 through 0.106.1 uses sync protocol 39. Protocol 41 exists only on main, since #10647 (merged Oct 17), and the main Docker image still calls itself 0.106.1. In the message, "local" is the desktop and "remote" is what the server reports (setup.ts). So your server is most likely running triliumnext/trilium:main.

To confirm, open https://<your-server>/api/setup/status (no login needed) and look for "syncVersion":41, or run docker compose images in your compose folder.

Pick one fix:

1. Keep the server and match the desktop. Install the Windows nightly (TriliumNotes-main-windows-x64.exe from the nightly release), or wait for v0.107.0, which is announced with protocol 41. Once 0.107.0 is out, set the server image to triliumnext/trilium:stable so it stops following main.
2. Take the server back to 0.106.1. Changing the tag alone won't work: main already migrated the database to version 242, and 0.106.1 exits with "The version of the database (242) is newer than what the application expects (240)". Stop the container. In the data folder, delete document.db, document.db-wal and document.db-shm, then copy backup/backup-before-migration.db to document.db (its date should match your upgrade). Set image: triliumnext/trilium:v0.106.1 and run docker compose up -d. You lose any edits made on the server since the upgrade. The Windows app keeps its own copy.

I checked this with both images. v0.106.1 (same digest as latest/stable) reports syncVersion 39, dbVersion 240. main reports appVersion 0.106.1, syncVersion 41, dbVersion 242. Setting up sync from the 0.106.1 container against the main one gives your exact error, and 0.106.1 won't start on a database created by main.