@xaddison the prune is done automatically when needed in the code. Most likely the containers that got removed are the ones that were "stopped". Cloudron runs cron jobs of apps in containers, for example. They will be in stopped state after finishing a run but will be reused in the next run. As for images, not sure what it cleaned up. Do you have the output of what it removed?
@girish Yes, that was changed. That was changed to domain2 while on still on VPS 1, where the initial mail location was domain1. So, I guess it didn't update properly back then. This is over a year ago. Maybe there was some glitch back then.
I tried to redo it just now by simply deleting "my" and retyping it, and there was a little message saying it was updating DNS, but only for the most recently added domain. I checked my main cloudron domain email settings under Status, and it still shows cloudron-domain1._domainkey, that the cloudron-domain2._domainkey DKIM key that others have.
I don't fully understand the DNS magic realm, and maybe it's fine that the DKIM domain doesn't actually match the actual domain, but now that I've discovered that my Cloudron is using three different DKIMs, I'd prefer to have them all use cloudron-domain2._domainkey.
Would I just navigate to where those keys are held on the VPS and delete them, and upon restarting the VPS cloudron will regenerate them, but properly using the current domain? My rDNS, or PTR record, uses my.domain2.com, same as the main dashboard domain, so don't these all have to match optimally?
The upgrade guides should mostly be identical for upgrading Ubuntu. The Cloudron guide has maybe couple of additional notes/configuration for making sure things are running after upgrade. What error are you hitting when upgrading following either of the docs? I suspect they hit the same error.
What I would like to do is that if I try to login to a new WP installation with the cloudron super-administrator user, an administrator user will be automatically generated in WP with my Cloudron access data. And if I enter as a common Cloudron user in WP, a user will be generated with their Cloudron access data with the role that I configure in the ldap plugin.
In this way, if I also changed my login details in Cloudron, it would also change on all WP sites.
This would also be good with the rest of the applications. It would simplify things a lot.
Thanks for the recommendation. PHPList looks like a "campaign" mailing list to send to external people. This is definitely useful but not quite what we were after.
More we are looking for mailing lists for internal people that maintains nice archives and people inside our group can subscribe to our de-subscribe to. Eg firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, etc. And so as people our interested in some of these topics they get naturally filtered to the different email lists... and we have internal archives of these lists. It works quite well as we currently have it. I just want to bring this sort of thing over to a cloudron server!
@girish editing the unit files to add Before=docker.service did not work for me. I can't see any of my files. However, if I try to mount these shares in the host system by editing fstab file, they are available on boot.
I can also confirm @msbt 's observations. If after boot, I go to the Volumes UI and delete, re-add shares, all these files become available. I then have to go the app (Jellyfin, Navidrome, etc.) and reboot the app to see the shares..
Thanks to @nebulon. After troubleshooting a few things on my network, we figured out that the access problem to my Cloudron is due to my ISP suddenly blocking ports 80 and 443. Please mark this issue as resolved!