Joplin Server: "WARNING: database "joplin" has a collation version mismatch"

Support
1

Operating system

Linux

Joplin version

3.3.3

What issue do you have?

Since the newest update of the Joplin Server running in Docker on Linux, I can't access it, and it doesn't sync and my published notes are not accessible. The Docker container was updated March 30th but this issue started a few days before that,

I haven't changed anything in my Docker or Joplin for many months. It has been running successfully for a few years.

When I check the logs I see the following below:

WARNING: database "joplin" has a collation version mismatch
2025-04-01 22:56:05.229 UTC [1066] DETAIL: The database was created using collation version 2.31, but the operating system provides version 2.36.
2025-04-01 22:56:05.229 UTC [1066] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE joplin REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

2

Which version of Joplin Server? To be sure try to install v3.3.13

3

It's the newest one, as my Docker automatically updates. In fact, I suspect that is the problem.

And, how do I check which version it is for sure? I can't log into my Joplin server?

If I do need to update, can I do that without risking losing my shared notes (specifically the public URLS)?

4

Just running docker images, docker container list, etc. should tell you what's running?

You can update at any time without losing shared notes as database migrations are done automatically (unless you've disabled automatic migrations, but probably not)

5

Thank you.

This is the output:

48d8f7c5ff32 joplin/server:beta "tini -- yarn start-…" 3 days ago Restarting (255) 1 second ago joplin-server-app-1

joplin/server beta 6c77f2de15b4 3 days ago 1.79GB

What is the best way to update it?

thanks again for your help.

6

You'd probably get better help in a Docker support forum as how you manage your Docker images is not specific to Joplin Server. Personally I'd update the version number in the docker-compose file because that's what I use but there are other ways.

7

Good news: once in Portainer, I re-pulled the image and it now works!

1 Like