Cloudron.io Staff
Agree that those are required for a real instance, I was just trying to understand if we can provide a package where the app does not crash on initial startup until those are set up.
All in all since we at least need changes to the TLS addon to also provide the root domain certs, we are looking at least to a package release after the next Cloudron version only. Just to keep expectations clear.
@wrapper this is quite an old issue. Can you create a new post with whatever issue you are facing?
Yes, we have to add this to the platform as a feature as well as think about how to make the DNS setup for those extra domains required. We have a policy that apps should "work" after installation. Do you know if there is a way that maybe those extra (sub)domains and thus their certs can be optional, just limiting the functionality of the app?
Since we test all app packages with the default (minimum) memory specified, I wonder how this had solved it. Is it possible that the system itself is running low on memory?
IIUC, you are using CIFS/NFS or some mount point for the backups . This mount is not working reliably, since you are unable to delete from the shell either. If so, this is a kernel/network/VPS level issue since Cloudron is not involved at that level . Is it an option to ask the support of the VPS provider or the mount storage provider?
@jdaviescoates @Stefan thanks, done, I have added them now. For the tags, look for the "tags" field in the CloudronManifest.json file in the https://git.cloudron.io/packages/ .
I am generally not in the group of AI = bad, however it likely just lacks lots of knowledge about the Cloudron internals, which make recommendations often not very useful in this area (yet).
Overall I am still not sure based on this thread why DNS was involved here and given that you hit 3 different addons with apparently diverse issues, maybe something unrelated to them individually caused the trouble.
We will add a few more helpers to the cloudron-support script for the future, to hopefully get down to such issues faster.
If you haven't deleted the server yet, maybe we could take a closer look via SSH, since you already invested much time in debugging. If you want that, please enable remote ssh support and send a mail to support@cloudron.io with your Cloudron details.
We are reworking the notification UI for Cloudron 9 at the moment and the reboot required hint will be fixed accordingly there. It has caused quite a few misunderstandings in the past as it currently is 
loomio and others like minio have multiple http ports (which are routed through the reverse proxy). If I understand the xmpp use-case correctly, then those are just alias endpoints not serving any http content. Even the current main domain will just produce a 404 when hit with a browser. The alias use is more like a bit of a workaround to get DNS setup as well as get valid certs.
