Deenius reported that after updating Docker Manager on their VPS—which hosts Discourse, WordPress, NGINX Proxy Manager, and Authentik—both Discourse and WordPress became unreachable, and NGINX Proxy Manager’s dashboard stopped responding, despite all containers appearing healthy in Portainer. They later resolved the issue by reverting recent changes made to the Authentik Docker Compose file, which had inadvertently broken NGINX Proxy Manager. However, they remain puzzled as to why the Docker Manager update triggered this cascade. tobiaseigen and Jagster clarified that this setup is considered unsupported because it diverges from the official Discourse installation, which does not include co-hosting WordPress or using reverse proxies like NGINX Proxy Manager. While unsupported installations won’t receive official support, community members may still offer help. Deenius asked for clarification on what “unsupported” meant, noting they followed official Discourse instructions, but tobiaseigen reiterated that combining Discourse with WordPress on the same VPS is not supported. Jagster added that while unsupported setups are off-topic for the Support category, many such issues have still been resolved by the community.
Hi, everyone. Something strange happened to me today.
I have a VPS server with Discourse forum and WordPress installed on it. I also have NGINX Proxy Manager and Authentik installed on it.
I updated Docker Manager. However, during the installation, Discourse and WordPress stopped working. UptimeRobot informed me about this by email.
Now, when I try to open my WordPress or Discourse forum website, I get the message “This website is not available.”
I can’t even access the NGINX Proxy Manager dashboard, which I normally access via npm.mywebsite.com. I tried exposing port 81, but I still can’t access the dashboard.
When I look to my Portainer, all containers are running. I tried restarting them, but nothing changed.
It seems that the problem is with NGINX Proxy Manager. It just stopped routing my services. Has this ever happened to any of you during a Docker Manager update? Do you have any explanation or solution? Thank you.
A month ago, I made a few changes to the Authentik Docker Compose file, which caused NGINX Proxy Manager to malfunction. Now everything is working again.
What I can’t figure out, though, is how updating Discourse Docker Manager triggered a chain of events that led to other applications malfunctioning. If anyone has any ideas about what might have happened, I’d love to hear them.
Hi Daniel! You have an unsupported install. We don’t recommend diverging from the official install and it’s not feasible for us to support you here if you do.
And unsupported in this context means you won’t get any official support from the team, and because this category is, well, ment to be a support channel to supported things, you are kind of off topic too.
Un-supported/can’t get support doesn’t mean someone from the community and even from the team wouldn’t or couldn’t help you, though. We have here tons of un-supported and solved questions.