What's new
Panelica Community Forum

Welcome to the official Panelica Community Forum — the central hub for server administrators, developers, and hosting professionals. Register a free account today to access technical discussions, product announcements, feature requests, and direct support from the Panelica team. Be part of the growing community shaping the future of server management.

Solved Forums for Docker

Drakon

New member
Beta Access
Hi Drakon,

Thanks for the suggestion. Our one-click deployment catalog currently has 102 application templates, but you are right — Discourse and Codoforum are not among them.

To be upfront, neither is an "add it right away" case for us, and I want to share why openly:

  • Discourse: Its official installation is managed by its own launcher script and templated bootstrap process; running it from a single container or a simple compose file is not officially supported. It can be forced into our isolated one-click model, but it would be fragile — and we verify that every template actually deploys and runs before we publish it, a guarantee we cannot honestly make for Discourse today.
  • Codoforum: It is PHP + MySQL based, so architecturally it resembles apps already in our catalog (like BookStack); however, there is no officially maintained Docker image for it, which means we would have to build and maintain our own image.

We have recorded both as feature requests and will keep evaluating them. In the meantime, one small ask: if the Discourse or Codoforum teams ever publish an official, maintained Docker image, please let us know — the moment an official image exists, we can add both to the catalog with confidence.

If what you need is forum/community software, would you like us to add an alternative with more mature Docker support instead? Just say the word and we will gladly look into it.

Thanks again — requests like this help us shape the catalog.
 
Here you go — this is now live in the latest update. Discourse, Lemmy and Flarum are available as one-click app templates under Docker Manager → App Templates.

Each one deploys its full stack automatically (PostgreSQL/MariaDB, Redis where needed, and the pict-rs image server for Lemmy), waits for the database to be ready before it installs, and creates the admin account on first boot — no manual setup wizard and no email-confirmation step. Just update your panel, open App Templates, and click Deploy.

We looked at Codoforum too, but it has no maintained Docker image, so we left it out for now. Give the three a try and let us know how they run for you!
 
It's been doing this for about an hour. I also tried /admin and same thing there too.
 

Attachments

  • Site-undergoing-maintenance-09-03-2026_06_43_PM.png
    Site-undergoing-maintenance-09-03-2026_06_43_PM.png
    43.5 KB · Views: 2
It's been doing this for about an hour. I also tried /admin and same thing there too.
Yes, we have tested https://test.panelica.cloud/ and confirmed that there is an issue. Our team is currently working on it and investigating the cause.

Please give us a little time to resolve this. We appreciate your patience and will keep you updated.
 
Lemmy gives an error of no access port and won't let you link a domain because of it.

Discourse still sits and says it's being setup and in maintenance.
 
Could you please try again and let us know the result?

Same thing, just sits there with:


I even deleted it all and re-installed it.

The Lemmy install won't let you link a domain because it gives an error that there are no exposed ports.
 
What we are actually trying to explain is that the functionality works correctly in the development environment, but it is not working reliably in the production environment.

The main reason is that many of these projects do not provide sufficiently stable or production-ready installation images. Even when we make the necessary adjustments and get everything working, there is still a possibility that future updates to those projects may introduce breaking changes again.

For this reason, we would appreciate some additional time. Over the next 7–14 days, we will repeatedly test the installation and update processes across different scenarios to ensure the implementation is as stable and reliable as possible.

We will keep you informed and provide you with an update once we have completed the testing.
 
Absolutely, do what you need to do to fix it. I am not in a hurry to have it done tomorrow, Thank you for your efforts and all you do for us Administrators.
 
Hi Drakon,

Thank you again for your patience — and for reporting this so clearly. The testing round we promised is finished, and everything you ran into is now fixed and live in the stable channel.

Please update your panel first (Updates page): Panelica Server 1.0.513 and Panel Frontend 4.5.326 or newer.

What changed since your last attempt:

  • Lemmy "no exposed ports", cannot link a domain — the template was rebuilt around a single web entry point (a proxy in front of the backend, frontend and image server), so the stack now exposes one port and domain linking works normally.
  • Discourse stuck on "setting up / maintenance" — deployment now waits for the database to be ready before the app bootstraps, and the admin account is created on first boot. We re-ran full clean install and removal cycles on our own production server and registered/posted as a normal member to confirm it end to end.
  • Link domain returning "Invalid request" — the quick Link action sent the port in the wrong format. Fixed.
  • Subdomain links — the panel now shows and opens the subdomain everywhere (dropdown, container card, search) instead of falling back to the parent domain.
  • After linking a domain, the panel now warns you about environment variables that still point at the old IP:port address, so assets do not stay pinned to the old URL.
  • Deleting a container with volumes now really removes its named volumes instead of leaving them behind.
  • Flarum sign-ups no longer fail with a 500 error on a server without SMTP configured.

One note for your existing installs: since the templates themselves changed, please remove the old Discourse/Lemmy containers and deploy them again after updating — an update alone will not repair a stack that was created with the previous template.

Please give it another try when you have a moment. If anything still does not work for you, open a ticket from your customer panel with the details (which template, the deploy result and the container logs) and we will go through it with you directly.
 
Back
Top