Solved Version mismatch local & server

[rmdes]

I'm wondering how to avoid this in the future, or at least, always have the server version upgrade before the local client, otherwise you end up with a local client that can't sync and an server version that miss latest notes made locally.

My desktop client upgraded and is now version 22 while server version is 21

any tip to avoid this altogether ?

[fbartels]

Something like this was why I stopped using Standardnotes. I was running it selfhosted, but was using their snap for the desktop app. The desktop app was updated, which broken the compatibility with my backend installation.

The only real way that you yourself could deal with this is by disabling automatic updates on your desktop and only updating once you have verified that both parts (client and server) still work together.

The way that bigger companies are dealing with this, is by providing a software way to upgrade, e.g. by adding warning popups that the client and server versions are soon no longer compatible and urging you to upgrade either one of those.

[girish]

Where are these protocol version numbers (21/22) coming from? I don't see them on Trilium GitHub atleast. https://github.com/zadam/trilium/wiki/Upgrading-Trilium#sync-compatibility says the release notes will say any protocol version changes but I don't see them in https://github.com/zadam/trilium/releases . Maybe a question for the upstream project?

[rmdes]

@girish Good point, I thought this was coming from cloudron package
I'll investigate where this is coming from further, thanks for the hint !