Self-hosted Joplin Server stopped being accessible (no sync and public notes not available)

Operating system

Linux

Joplin version

3.4.3

Desktop version info

Server version

Sync target

Joplin Server

What issue do you have?

Since the server update to 3.4.3 a few days my self-hosted Joplin server is no longer accessible via local network nor my custom sub-domain. Thus, syncing doesn't work nor do my published notes (which I have dozens - I use them for my business).

I am self hosting the Joplin server in Docker on Linux

I normally sync between Joplin linux desktop and Android app.

I've tried the following image tags: beta, latest, 3.4.2 and 3.4.3.

I have, of course, restarted both containers multiple times, and rebooted the computer.

FYI, all of my other containers in Docker work.

This is strange as I've gone years with no problem with my self-hosted Joplin server - in fact I use it to host public articles I've written for my business, which is why I am hoping someone can help me.

PS. Looking at the attached logs, this stands out in the DB log:

"The database was created using collation version 2.31, but the operating system provides version 2.41."

Ps I've considered starting over and rebuilding it from scratch but I don't want to lose the URL's of my published notes.

Log file

_joplin-server-app-1_logs.txt (6.08 KB)
_joplin-server-db-1_logs.txt (12.1 KB)

If it matter, in my Docker Compose I have

    image: postgres:15

Should that be 16? (I’ve had this docker server running for a while!)

I searched the forum for the error you are seeing and the only previous instance was one you reported.

Back then it was suggested that it may be a docker issue?

Anyway, I do not know if the database version could be the cause of your problem but this file on GitHub https://github.com/laurent22/joplin/blob/dev/packages/server/src/db.ts says that the minimum Postgres version is 12, so maybe it is not.

export const versionCheck = async (db: DbConnection) => {
	if (isPostgres(db)) {
		// We only support Postgres v12+
		// https://github.com/laurent22/joplin/issues/9695
		// https://www.postgresql.org/docs/current/rules-materializedviews.html
		const minPostgresVersion = '12.0';

In case you are not aware, if you do decide to try changing database versions it can require more than just updating your docker-compose file. This post helped me to migrate from Postgres v15 to v16:

1 Like

Thank you for your reply. Funny story is that when I searched for the issue I also came up with my own post, as you did! Back then, simply re-pulling the image fixed it, but not this time.

I will look into the upgrading the postgres.

If I start from scratch and reinstall the Joplin Server and re-sync to my existing Joplin Desktop will I lost the URLs of my published notes? Are the published notes’ URLs stored in the Server or also in the desktop Joplin?

thank you very much for your help!

As I understand it the server does all the work when it comes to publishing / sharing.

If the published notes are important to your work have you considered a Joplin Cloud subscription so all of this updating and maintaining of the server becomes someone else's problem? :slight_smile:

I'm nothing to do with Joplin (just another user) so this really is a suggestion and not a sales pitch !!!!!!!

I thought about using Joplin Cloud. However, my server is tied to my domain, so my published notes’ URL are tied to that domain. Such as: https://joplin.mydomain.com/shares/m6M9umL1tHDAOll2WHztIG

Thanks for your help! I’m just befuddled as to what happened? I’ve been hosting it for at least 2+ years, with only the one hiccup being my previous post.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.