A matching desktop version doesn't exist for server version 37

[olegedly]

Description

stack: Error: Could not setup sync since local sync protocol version is 36 while remote is 37

Sync broke for me because I updated the Docker image to the latest version, but there's no compatible desktop version.

TriliumNext Version

0.102.1

What operating system are you using?

Other Linux

What is your setup?

Local + server sync

Operating System Version

Linux eos 6.19.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 19 Mar 2026 16:33:17 +0000 x86_64 GNU/Linux

Error logs

12:55:44.632 Sync failed: 'Could not setup sync since local sync protocol version is 36 while remote is 37. To fix this issue, use same Trilium version on all instances.', stack: Error: Could not setup sync since local sync protocol version is 36 while remote is 37. To fix this issue, use same Trilium version on all instances.
at Object.eAs [as hasSyncServerSchemaAndSeed] (/usr/lib/triliumnext/app.asar/main.cjs:1731:854)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async yQr (/usr/lib/triliumnext/app.asar/main.cjs:1731:3256)
at async /usr/lib/triliumnext/app.asar/main.cjs:1731:2754
at async Object.Fzr [as doExclusively] (/usr/lib/triliumnext/app.asar/main.cjs:19:3678)
at async Zze (/usr/lib/triliumnext/app.asar/main.cjs:1731:2606)
12:56:37.698 200 POST /api/tree/load with 5804 bytes took 0ms
12:56:37.730 204 PUT /api/options with 0 bytes took 1ms
12:56:37.766 200 GET /api/note-map/_backendLog/backlink-count with 11 bytes took 1ms
12:56:37.766 200 GET /api/notes/_backendLog/attachments with 2 bytes took 0ms

[dosubot[bot]]

Hi @olegedly! I'm Dosu and I’m helping the Trilium team.

This sync protocol mismatch occurs because your desktop and server are running different versions. The current version 0.102.1 uses sync protocol v37, which was introduced on March 3, 2026 to prevent data loss from unsupported note types.

If your desktop is showing protocol v36, you may be running an older desktop version even though it reports as 0.102.1. I'd suggest:

1. Verify your desktop version — Check Help → About to confirm the exact version
2. Re-download the desktop client from the latest release to ensure you have the actual 0.102.1 build with protocol v37

If you need a workaround, you can roll back the Docker server by pinning to a specific tag (e.g., triliumnext/trilium:v0.101.0). However, databases are migrated on upgrade and older versions cannot read them — you'd need to restore from a backup taken before upgrading.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[eliandoran]

Hi,

Can you confirm which Docker tag did you use?

Regardless, sync version 37 is not part of any release yet, so most likely you tried the main tag which tracks the latest development. You can either roll back your server and restore from a backup, or update your Desktop to the latest nightly.