No Subscribers/Lists after upgrade

[romainmp]

Version:

• listmonk: v3.0.0, upgrading to 4.1.0
• OS: Truenas Scale 24.10.0.2

Description of the bug and steps to reproduce:
After upgrading the app to 4.1.0 and logging back in to Listmonk, dashboard displays correct counters about lists, subscribers etc... but can't find anything in admin/lists or admin/subscribers
Bounces are OK though ...

Using pgAdmin I can see that lists, subscribers and subscriber_lists tables are correctly populated.

Is there a command to run to upgrade DB so that I can get back my data ?

Running listmonk --upgrade returns the following :

> # docker exec -it ix-listmonk-listmonk-1 sh
/listmonk # ./listmonk --upgrade
2024/11/30 17:43:59.996954 main.go:107: v4.1.0 (0a27de1 2024-11-12T18:42:26Z, linux/amd64)
2024/11/30 17:43:59.997026 init.go:163: reading config: config.toml
2024/11/30 17:43:59.997181 init.go:303: connecting to db: postgres:5432/listmonk
** IMPORTANT: Take a backup of the database before upgrading.
continue (y/n)?  y
2024/11/30 17:44:02.256658 upgrade.go:68: no upgrades to run. Database is up to date.

[knadh]

hm, that is very strange. listmonk v4.1.0 upgrade does nothing to lists and subscribers data.

• Ctrl+Shift+R fixes it?
• Do you see any Javascript errors in your browse console? (F12 key -> Console tab)

[romainmp]

hm, that is very strange. listmonk v4.1.0 upgrade does nothing to lists and subscribers data.

• Ctrl+Shift+R fixes it?
• Do you see any Javascript errors in your browse console? (F12 key -> Console tab)

First thing I tried was cleaning cache and cookies. No effect

Only error is when trying to log out :
AxiosError: Request failed with status code 502

[knadh]

AxiosError: Request failed with status code 502

502 indicates that the server is not running. Either listmonk service is down, or there's an issue with the reverse proxy configuration (if you have one, like Nginx).

You might want to restart your listmonk installation.

[romainmp]

AxiosError: Request failed with status code 502

502 indicates that the server is not running. Either listmonk service is down, or there's an issue with the reverse proxy configuration (if you have one, like Nginx).

You might want to restart your listmonk installation.
I restarted every container, including proxy (Traeffik) and it worked. Thank you

I still don't understand how I could exec commands and see the new warning message about the admin password being set in the environment variables if listmonk was not running ...

[radioboss]

Had the same issue; it was fixed by removing admin_username/admin_password from the config file and restarting Listmonk.