Hey! Did you find the solution to this issue?

I checked the log which says:
“there are 1 pending database upgrade(s): [v5.1.0]. The last upgrade was v5.0.0. Backup the database and run listmonk –upgrade”

How do I run listmonk –upgrade ? I would really appreciate any help or instructions. Thank you, Ben

I installed Listmonk on Lightsail using Rameerez’s very helpful instructions. Everything worked fine for a month. However, since yesterday, I’ve been experiencing the following problem: the listmonk-app-1 docker no longer starts correctly and keeps trying to restart. I’ve already rebooted Ubuntu and also stopped and restarted it. The result remains the same. “sudo docker container ls” returns the following information:

9a659c3011b4 listmonk/listmonk:latest “docker-entrypoint.s…” 16 minutes ago Restarting (1) Less than a second ago listmonk-app-1

5dc4ff7ef8e7 postgres:13-alpine “docker-entrypoint.s…” 16 minutes ago Up 16 minutes ago (healthy) 5432/tcp listmonk-db-1

This also means that I can no longer launch the Listmonk login page and instead receive an error message: 502 Bad Gateway nginx/1.18.0 (Ubuntu)

Can you please help me so that the listmonk-app-1 docker starts correctly again (and doesn’t permanently restart) and the Listmonk login page is displayed again.

Thanks for sharing, Michael! You may also want to try Hetzner or DigitalOcean (both alternatives to AWS Lightsail) – they offer cheap instances and good monitoring too.

I had a similar thing happen to me. I suspected Rameerez was right about his memory suspicion, but oddly Lighsail doesn’t display your RAM usage in the metrics tab even though it’s the first parameter of the product tiers. There were probably other ways to solve this, but I created a snapshot of my instance, spun up a larger capacity instance from that snapshot, and added in CloudWatch monitoring to keep an eye on the RAM usage. So far, things are running smoothly, but we’ll see when I get out of sandbox if 2GB of RAM was enough.

I suggest you check the Listmonk logs / web server logs for info on why it’s failing. ChatGPT or Claude can help you navigate this: ask them where the logs probably are, how to interpret the error messages you see, how to fix them, etc.

My only guess without more information would be that your instance is too small, and it doesn’t have enough memory / CPU to run the Listmonk service for a sustained period of time. But that’s only one guess. You’ll find the right solution after figuring out what the error is by reading the logs.

I am using Lightsail US region, SES is on London, now after running sometime listmonk is not accessible from webbrowser, after restarting it will work fine again, but why it is stopping again and again. any solution?

I believe you’re confusing terms here: the firewall (ufw, or Lightsail’s own firewall) doesn’t have anything to do with what you’re asking. What you’re worried about is API authentication, and it turns out most of the API endpoints in Listmonk are in fact authenticated and password protected.

If you try, for example, getting /api/subscribers on a browser window that doesn’t have a Listmonk session logged in (try an Incognito window, for example), you’ll just see the username / password prompt, and no results. The official docs on the Listmonk API are quite good: https://listmonk.app/docs/apis/subscribers – you’ll see all endpoints that need auth requiring username and password in the curl call.

One endpoint that does not require auth, for example, is POST /api/public/subscription, which is used by the embeddable newsletter suscription form so that people can sign up for your (public) newsletter.

Thanks! Happy you found it useful.

Just added an extra step explaining how to deal with bounced emails and complaints to automatically blocklist offending email addresses, thanks for the feedback!