Listmonk lost configuration settings after Reboot of NS 8

Looks good so far. Butt he question is, what i have to put into this field.

Screenshot 2025-08-15 135143

The fqdn listmonk.mydomain.com dont work. Or is it a problem with the firewall of NS 8 and i have to open port 9000?

Sunny greetings from the European Africa ( Germany with actually 34 ° C) :hotsprings:

1 Like

let me workout a solution for the same

2 Likes

i tried setting the url but the application crashed it only accepts the address 0.0.0.0:9000

Is it not possible to change from 0.0.0.0:9000 to the fqdn:9000?

environment: # The same params as in config.toml are passed as env vars here.
LISTMONK_app__address: 0.0.0.0:9000
LISTMONK_db__user: *db-user
LISTMONK_db__password: *db-password
LISTMONK_db__database: *db-name
LISTMONK_db__host: listmonk_db
LISTMONK_db__port: 5432
LISTMONK_db__ssl_mode: disable
LISTMONK_db__max_open: 25
LISTMONK_db__max_idle: 25
LISTMONK_db__max_lifetime: 300s
TZ: Etc/UTC
LISTMONK_ADMIN_USER: ${LISTMONK_ADMIN_USER:-} # If these (optional) are set during the first docker compose up, then the Super Admin user is automatically created.
LISTMONK_ADMIN_PASSWORD: ${LISTMONK_ADMIN_PASSWORD:-} # Otherwise, the user can be setup on the web app after the first visit to http://localhost:9000
volumes:
- ./uploads:/listmonk/uploads:rw

that is how it used to be like before feat: updated port and address · geniusdynamics/ns8-listmonk@3d01217

Hi @oneitonitram

When I use this docker-compose.yml and install it on my server (Ubuntu 24) via Portainer, it works with 192.168.xxx.xxx:9000.

1 Like

When i use http://listmonk.mydomain.com without any portnumber, it’s usable.

2 Likes

You changed the fdqn in the list monk interface or in the docker compose

I changed the fdqn in the list monk interface.

Yeah in the list monk interface its possible but when you change it in the docker compose the docker container crashes

1 Like

If I change that on the listmonk page and it works, then that’s fine.

1 Like