Turns out that Cloudron hit the same issue as https://forum.cloudron.io/topic/11276/cloudron-update-to-7-7-0-postgresql-does-not-start?_=1723244919333 and the fixed worked there also.

Hi, we did not initiate an update manually. According to the logs, Cloudron updated to v8.0.3 this morning at 6:58. The message "removing containers for upgrade" was still there at midday. Error message when going to an app: "This app is currently not responding. Please try refreshing the page in a few minutes." After a manual reboot, all apps were "Configuring (Queued)" for a while. Now the first apps are running again. Yeah

Thank you that made me understand the differences quite well. Sadly it seems like the issue is not resolved yet though. The Outlook client seems to stay slow. It was just shortly working a bit better it seems. What I don't understand is the following though: Only the modern Mac Outlook is slow/buggy. If I switch to legacy outlook there are no Problems. Thunderbird is having no Problems as well, same with other clients. I found out though that when I enable Offline Mode in the modern Outlook Mac client, then the search is not slow anymore. Still there is the problem that Attachments are buggy and when you try to open them Outlook says that they have to be redownloaded to open them (which does not work). The modern Outlook for Mac does work with other IMAP clients though. So It's not Purely an Outlook problem and not Purely a Cloudron Mail problem. There just seems to be a problem in the communication between them. I just seem to no be able to debug it. Does anyone have an idea what it could be?

I will mark this as solved, but please open a new topic with the crash report.

Since this question seems to come up often, I wonder if we should just show the timezone in brackets everywhere in the UI. @nebulon ?

@lilian I think you misunderstood what I said (or maybe I misunderstand your setup). I am asking you to mount your external/addition disk under /srv instead of under /mnt/volumes/04067a3544294e0fa162392e066337cf . Once you mount under /srv , you can then add it as a Volume with Filesystem or Mountprovider type. It was a bug that we allowed volumes to have host path under /mnt/volumes . This is fixed now for next release (https://git.cloudron.io/cloudron/box/-/commit/21705a0e966ef998e836e6b7fed0da00dadfee79)

@nebulon Okay, thank you very much. I think it could be good also keep some options for non-developers that allow users to import and export mailboxes, avoiding REST APIs that require deep knowledge of development. This aligns with part of Cloudron's payoff: 'Self-hosting has never been simpler.' Thank you very much!

Can you check the update task logs for the error? You can find those in the Settings view in your Cloudron dashboard.

Ah, sorry. That was my mistake. The update worked now (maybe after upgrade Cloudron to 8.0.3). Now the app is running version 4.0.0-1.

We have a media group that the app's user is part of. See https://docs.cloudron.io/volumes/#sharing

Such a long reboot time is quite unusual indeed. Maybe your server provider has some infra issues?

Thanks for sharing this. From the logs (sent to our support) this was triggered by an update to 8.0.3 where upgrading the mongodb instance didn't succeeds correctly. Unfortunately there is nothing much in the mongodb logs besides a plain "core dump" crash. But as @hayoken2000 outlines, one can always purge mongodb data and let it start fresh, then restore those apps.

Great that you managed to resolve it quickly and thanks for the update here with the solution.

The only message was only related to PTR. And there was no other message. Maybe it was a special case or a problem with the request and the question was whether from my server or on the provider's side. After I clicked sync DNS, I left it for another 24 hours just to be sure, because the proprogation could have been prolonged. After 24 hours there was still a problem , then I did a record analysis and noticed as I wrote above one record A was not updated. In general, the situation embraced. You can close the topic only waiting for the improvement of the results from PTR. Generally I have changed but FCrDNS has not been updated.

As you mention, you need a separate account for accessing the app library. Do you see any errors in the browser console? Alternately you can also sign up first at https://console.cloudron.io/#/signup and then use that account to login via your Cloudron dashboard.

This is handled in support by now. The AAAA records for that domain are not set up.

Looks like that was the fix, now it doesn't change the A and AAAA records of the email server, and Cloudron can still use my External SMTP connection while having the Mail Server Location set to "cloudron.blockbluemedia.com".

@timbo I have practically zero spam with the rules mentioned in my post and abusix DSNBL (https://abusix.com/) - the free tier is sufficient. Do you have catch-all enabled?

I've solved the docker daemon problem, I just couldn't start my docker on my pc. But for the rest of my problems I still don't have an answer.

Always good to hear, if things are fine