NethServer Version: 8
Module: Listmonk
I installed and configured Listmonk to try it out. The app seems really useful. SMTP can be configured without any problems. Creating new users also works right away. The only problem is that the settings do not survive a reboot of the NS 8 and have to be re-entered after restarting the VM.
Did I perhaps overlook a setting, or is this possibly a bug in the software?
Regards…
Uwe
Sorry for this
Let me check the issue
Can you help me test this
add-module ghcr.io/geniusdynamics/listmonk:dev 1
Yes, i will do it after my work in the afternoon and then i will give you a feedback.
2025-08-07T11:24:58+02:00 [1:listmonk1:systemd] Stopping Podman listmonk-app.service...
2025-08-07T11:24:58+02:00 [1:listmonk1:systemd] libpod-63a82d1f9336a4b4de1dd3c3dcb69887cd5dbe81fb3c5e713e7242d6e87ef154.scope: Consumed 2.209s CPU time.
2025-08-07T11:24:58+02:00 [1:listmonk1:listmonk1] 63a82d1f9336a4b4de1dd3c3dcb69887cd5dbe81fb3c5e713e7242d6e87ef154
2025-08-07T11:24:58+02:00 [1:listmonk1:systemd] listmonk-app.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
2025-08-07T11:24:58+02:00 [1:listmonk1:listmonk1] 63a82d1f9336a4b4de1dd3c3dcb69887cd5dbe81fb3c5e713e7242d6e87ef154
2025-08-07T11:24:58+02:00 [1:listmonk1:systemd] listmonk-app.service: Failed with result 'exit-code'.
2025-08-07T11:25:01+02:00 [1:listmonk1:listmonk-app] Launching listmonk with user=[root] group=[root] PUID=[0] PGID=[0]
2025-08-07T11:25:01+02:00 [1:listmonk1:listmonk-app] 2025/08/07 09:25:01.581557 main.go:106: v5.0.3 (48643aa9 2025-07-06T16:14:03Z, linux/amd64)
2025-08-07T11:25:01+02:00 [1:listmonk1:listmonk-app] 2025/08/07 09:25:01.581803 init.go:169: reading config: /config.toml
2025-08-07T11:25:01+02:00 [1:listmonk1:listmonk-app] 2025/08/07 09:25:01.582194 init.go:309: connecting to db: postgresql-app:5432/listmonk
2025-08-07T11:25:01+02:00 [1:listmonk1:listmonk-app]
2025-08-07T11:25:01+02:00 [1:listmonk1:listmonk-app] ** first time installation **
2025-08-07T11:25:01+02:00 [1:listmonk1:listmonk-app] ** IMPORTANT: This will wipe existing listmonk tables and types in the DB 'listmonk' **
2025-08-07T11:25:02+02:00 [1:listmonk1:listmonk-app] continue (y/N)? 2025/08/07 09:25:02.581272 install.go:96: no superadmin user created. Visit webpage to create user.
Where I already created a new first user before restart. And indeed settings are lost when accessing the FQDN:
HTH
I think the issue is that yes is piped to --install regardless if the db already exists: ns8-listmonk/imageroot/systemd/user/listmonk-app.service at main · geniusdynamics/ns8-listmonk · GitHub
Can someone test to see if the problem has been resolved
use this
add-module ghcr.io/geniusdynamics/listmonk:dev 1
It doesn’t work here, the listmonk-app container is not starting.
It seems there’s a port missing in the config:
2025-08-07T17:22:05+02:00 [1:listmonk1:listmonk-app] 2025/08/07 15:22:05.812851 init.go:895: error starting HTTP server: listen tcp: lookup tcp///listmonk.nst.at: unknown port
Same problem here.
I did, please see above
Working on it
Can some one test it now on my part it seems fine
add-module ghcr.io/geniusdynamics/listmonk:dev 1
Installed and configured, provided user and pass. Going to FQDN:
Clicking login:
2025-08-08T05:37:10+02:00 [1:listmonk2:listmonk-app] 2025/08/08 03:37:10.833692 init.go:309: connecting to db: postgresql-app:5432/listmonk
2025-08-08T05:37:10+02:00 [1:listmonk2:listmonk-app]
2025-08-08T05:37:10+02:00 [1:listmonk2:listmonk-app] ** first time (idempotent) installation **
2025-08-08T05:37:10+02:00 [1:listmonk2:listmonk-app]
2025-08-08T05:37:10+02:00 [1:listmonk2:postgresql-app] 2025-08-08 03:37:10.956 UTC [54] ERROR: relation "settings" does not exist at character 22
2025-08-08T05:37:10+02:00 [1:listmonk2:postgresql-app] 2025-08-08 03:37:10.956 UTC [54] STATEMENT: SELECT count(*) FROM settings
2025-08-08T05:37:11+02:00 [1:listmonk2:listmonk-app] 2025/08/08 03:37:11.506671 install.go:90: LISTMONK_ADMIN_USER should be min 3 chars and LISTMONK_ADMIN_PASSWORD should be min 8 chars
2025-08-08T05:37:11+02:00 [1:listmonk2:systemd] listmonk-app.service: Main process exited, code=exited, status=1/FAILURE
2025-08-08T05:37:11+02:00 [1:listmonk2:listmonk2] cafd62c0bb006bd175891437145dc7bfc50639989eb27353e7e83cb3b34828c3
2025-08-08T05:37:11+02:00 [1:listmonk2:systemd] listmonk-app.service: Failed with result 'exit-code'.
I’ve used ‘admin’ and ‘admin’ as credentials during configuration.
Both mailing archive and subscribe links at the login window:
http://localhost:9000/subscription/form
http://localhost:9000/archive
Are these ports ok?
2025-08-08T05:37:13+02:00 [1:listmonk2:postgresql-app] 2025-08-08 03:37:13.472 UTC [1] LOG: starting PostgreSQL 15.5 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20231014) 13.2.1 20231014, 64-bit
2025-08-08T05:37:13+02:00 [1:listmonk2:postgresql-app] 2025-08-08 03:37:13.472 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-08-08T05:37:13+02:00 [1:listmonk2:postgresql-app] 2025-08-08 03:37:13.472 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-08-08T05:37:13+02:00 [1:listmonk2:postgresql-app] 2025-08-08 03:37:13.475 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
Yeah
I think this you manually have to change i tried setting the base url but the app crashes
So i had to put ip “0.0.0.0:9000” for it to work
Never saw this let me enforce this
Any news from your side?
hy, did you try installing this version: Release 1.1.0 · geniusdynamics/ns8-listmonk
No…, in the moment my machine is clean. But i can test it for you.
ok kindly test that and repor tif the issues have been resolved
I missed this announcement of this release for I thought a dev release was expected, not a dot release.