NS8-Joplin Server App

oneitonitram · July 29, 2025, 2:35pm

i guess there is the answer, ok, let me work on this

oneitonitram · July 30, 2025, 5:24am

this actually seesm to be a new feature in version 5.5 of podman

mrmarkuz · July 30, 2025, 9:46am

I installed joplin 1.0.5 and there’s no bad gateway but podman version is 5.4.0.

add-module ghcr.io/geniusdynamics/joplin:1.0.5

But postgres is still not working, sqlite is used, from the logs:

2025-07-30T11:37:23+02:00 [1:joplin1:joplin-server] 09:37:23 0|app  |   client: 'sqlite3',

You need to set following variable for joplin-server to make joplin use postgres:

DB_CLIENT=pg

EDIT:

It should be enough to add the following to postal-server service file:

    --env DB_CLIENT=pg \

LayLow · July 30, 2025, 10:24am

Just curious, what OS details pls?

mrmarkuz · July 30, 2025, 10:26am

Rocky 9.6

LayLow · July 30, 2025, 10:30am

So far for the only ‘Rocky 9.6 setupa’ are effected by ‘bad gateway’ then?

oneitonitram · July 30, 2025, 10:46am

so @LayLow you have faced bad gateway for both joplinserver as well as postalserver on your server, running rocklinux, is the podman version 5.4

mrmarkuz · July 30, 2025, 10:54am

Just to clarify:

Joplin is working here on Rocky 9.6 using podman 5.4.

LayLow · July 30, 2025, 11:34am

Yes it is

danb35 · July 30, 2025, 3:10pm

I see an update available to 1.0.6; does this address the email issue? Only change in the release notes is to the database.

kemboielvis22 · July 30, 2025, 6:20pm

This has been set in in joplin.env

github.com/geniusdynamics/ns8-joplinserver

imageroot/actions/create-module/10configure_environment_vars

main


      
          POSTGRES_PASSWORD = generate_random_password(16)
          
          db_config = {
              "POSTGRES_ROOT_HOST": "joplin-pgsql",
              "POSTGRES_DATABASE": POSTGRES_DB,
              "POSTGRES_USER": POSTGRES_USER,
              "POSTGRES_PASSWORD": POSTGRES_PASSWORD,
          }
          agent.write_envfile("database.env", db_config)
          
          joplin_db_config = {
              "JOPLIN_DBENGINE": "pg",
              "JOPLIN_DBHOST": "joplin-pgsql",
              "JOPLIN_DBNAME": POSTGRES_DB,
              "JOPLIN_DBUSER": POSTGRES_USER,
              "JOPLIN_DBPASS": POSTGRES_PASSWORD,
          }
          agent.write_envfile("joplin-db.env", joplin_db_config)
          
          agent.dump_env()

github.com/geniusdynamics/ns8-joplinserver

imageroot/actions/configure-module/10configure_environment_vars

main


      
          SMTP_ENCRYPTION = smtp_settings["encrypt_smtp"]
          SMTP_TLSVERIFY = "true" if smtp_settings["tls_verify"] else "false"
          app_config = {
              "APP_BASE_URL": APP_BASE_URL,
              "MAILER_ENABLED": SMTP_ENABLED,
              "MAILER_SECURITY": SMTP_ENCRYPTION,
              "MAILER_HOST": SMTP_HOST,
              "MAILER_PORT": SMTP_PORT,
              "MAILER_AUTH_USER": SMTP_USERNAME,
              "MAILER_AUTH_PASSWORD": SMTP_PASSWORD,
              "MAILER_NOREPLY_EMAIL": SMTP_USERNAME,
              "MAILER_NOREPLY_NAME": "JoplinServer",
          }
          agent.write_envfile("app.env", app_config)
          
          
          agent.dump_env()

i have set this hopefully it will work

kemboielvis22 · July 30, 2025, 6:20pm

@danb35 can you test and let me know if this fixes the issue

danb35 · July 30, 2025, 6:35pm

Well, updating lost all the users, again. Not OK.

Email isn’t sent on user creation, though I don’t know if it’s the same problem. Here’s what I get looking for “mail” in the joplin2 logs over the past several minutes:

2025-07-30T14:30:27-04:00 [1:joplin2:joplin-server] 18:30:27 0|app  | 2025-07-30 18:30:27: [error] App: 403: POST /api/sessions: 172.70.82.208: Invalid username or password: {"email":"dan@familybrown.org"}
2025-07-30T14:30:28-04:00 [1:joplin2:joplin-server] 18:30:28 0|app  | 2025-07-30 18:30:28: [error] App: 403: POST /api/sessions: 162.158.79.80: Invalid username or password: {"email":"dan@familybrown.org"}
2025-07-30T14:30:28-04:00 [1:joplin2:joplin-server] 18:30:28 0|app  | 2025-07-30 18:30:28: [error] App: 403: POST /api/sessions: 172.70.83.34: Invalid username or password: {"email":"dan@familybrown.org"}
2025-07-30T14:30:29-04:00 [1:joplin2:joplin-server] 18:30:29 0|app  | 2025-07-30 18:30:29: [error] App: 403: POST /api/sessions: 172.68.186.25: Invalid username or password: {"email":"dan@familybrown.org"}
2025-07-30T14:30:29-04:00 [1:joplin2:joplin-server] 18:30:29 0|app  | 2025-07-30 18:30:29: [error] App: 403: POST /api/sessions: 172.70.82.33: Invalid username or password: {"email":"dan@familybrown.org"}
2025-07-30T14:30:30-04:00 [1:joplin2:joplin-server] 18:30:30 0|app  | 2025-07-30 18:30:30: [error] App: 403: POST /api/sessions: 172.70.82.4: Invalid username or password: {"email":"dan@familybrown.org"}
2025-07-30T14:31:00-04:00 [1:joplin2:joplin-server] 18:31:00 0|app  | 2025-07-30 18:31:00: TaskService: Running #12 (Process emails) (scheduled)...
2025-07-30T14:31:00-04:00 [1:joplin2:joplin-server] 18:31:00 0|app  | 2025-07-30 18:31:00: TaskService: Completed #12 (Process emails) in 12ms
2025-07-30T14:32:00-04:00 [1:joplin2:joplin-server] 18:32:00 0|app  | 2025-07-30 18:32:00: TaskService: Running #12 (Process emails) (scheduled)...
2025-07-30T14:32:00-04:00 [1:joplin2:joplin-server] 18:32:00 0|app  | 2025-07-30 18:32:00: TaskService: Completed #12 (Process emails) in 8ms
2025-07-30T14:32:18-04:00 [1:joplin2:joplin-server] 18:32:18 0|app  | 2025-07-30 18:32:18: App: GET /admin/emails (200) (15ms)
2025-07-30T14:32:30-04:00 [1:joplin2:joplin-server] 18:32:30 0|app  | 2025-07-30 18:32:30: App: GET /admin/emails/1 (200) (6ms)
2025-07-30T14:33:00-04:00 [1:joplin2:joplin-server] 18:33:00 0|app  | 2025-07-30 18:33:00: TaskService: Running #12 (Process emails) (scheduled)...
2025-07-30T14:33:00-04:00 [1:joplin2:joplin-server] 18:33:00 0|app  | 2025-07-30 18:33:00: TaskService: Completed #12 (Process emails) in 9ms

kemboielvis22 · July 30, 2025, 6:47pm

Will check on this

Am not sure about this allow me to investigate further

danb35 · July 30, 2025, 6:53pm

I think the “invalid username or password” may result from the fact that I still have clients that are periodically trying to sync. I don’t see any errors in the log directly about sending mail, but logged or not, no mail is sent (and it also isn’t in my Junk folder).

mrmarkuz · July 30, 2025, 6:54pm

Not exactly. This is set:

…but this is needed to use postgres:

EDIT:

Sorry, it’s already here and it works in 1.0.6.

github.com/geniusdynamics/ns8-joplinserver

imageroot/systemd/user/joplin-server.service

main


      
          Restart=always
          ExecStartPre=/bin/rm -f %t/joplin-server.pid %t/joplin-server.ctr-id
          ExecStartPre=/usr/local/bin/runagent discover-smarthost
          ExecStart=/usr/bin/podman run \
              --detach \
              --conmon-pidfile=%t/joplin-server.pid \
              --pod-id-file=%t/joplin.pod-id \
              --cidfile=%t/joplin-server.ctr-id \
              --cgroups=no-conmon \
              --replace --name joplin-server \
              --env DB_CLIENT=pg \
              --env-file=smarthost.env \
              --env-file=%S/state/joplin-db.env \
              --env-file=%S/state/app.env \
              ${SERVER_IMAGE}
          ExecStop=/usr/bin/podman stop --ignore --cidfile %t/joplin-server.ctr-id -t 10
          ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile %t/joplin-server.ctr-id
          PIDFile=%t/joplin-server.pid
          Type=forking
          
          [Install]

kemboielvis22 · July 30, 2025, 7:13pm

@mrmarkuz have you tested joplin to see if it works

LayLow · July 30, 2025, 8:37pm

Can we settle on the naming convention here please?

Either Joplin or Joplin Server/Joplin-Server

TIA

mrmarkuz · July 30, 2025, 8:38pm

Yes, it works, postgres is used as database in 1.0.6.

oneitonitram · July 31, 2025, 3:37am

@danb35 this is the reason. the database was switched to pgsql, the other users should still be present in the inbuilt sqlite database, but the system is using pgsql now isntead of sqlite internal db