Actually what you have explained is correct and should work. The /app/data/local.yaml is exactly there for this use-case. Have you restarted the app after applying the changes, in order to have the app assets rebuilt?

I am not an expert on WordPress Multisite, but if the individual pages should have to be delievered on different subdomains/domains then this is not supported with Cloudron.

Is there anything which needs solving then or can it be closed? If this is a permissions issue, maybe the package needs to be adjusted?

this very much depends on your preferences. We have had great experience with all the ones listed at https://cloudron.io/get.html

Some longer time back, we removed that implicit email account creation. The dashboard domain now has nothing to do with the email accounts and email domains. You can manage them independently. Only the mailserver DNS remains to be bound to dashboard domain. This is what you would use to configure an email client.

Most likely this was due to the issue in the last release. If renewal is attempted but fails for some reasons you will get an email notification about that. Generally it will start trying to renew 1 month prior to expiration.

We did have an issue in our last release about certificate renewals not always happening correctly. This is fixed. However in your case you have to first login and manually refresh the certificates using the corresponding button in the dashboard. The easiest way in your case might be, to simply use another browser to for that one-time login to avoid the HSTS issue, or you can purge your browser history from your dashboard domain and restart the browser, then you will be able to add a temporary exception.

Sorry about all that inconvenience.

That may depend on what you want to configure. Maybe you can be more explicit?

This should not be the case, can you verify that unbound is working correctly https://cloudron.io/documentation/troubleshooting/#unbound

Most likely the docker images take up all that space and tools like du are known to not report on this properly as mentioned in https://cloudron.io/documentation/storage/ Please use docker system df to determine the docker image sizes.

For further technical details if you are interested, there is some more explanation at https://stackoverflow.com/questions/50589971/diffrence-between-real-and-showed-by-docker-system-df-disc-usage

Further as stated earlier, you may just wait for the next release and the reporting within the dashboard is handling this already for you.