This is implemented in Cloudron 8

@ekevu123 the manifest error here refers to the docker image manifest. That part of the error message is from your upstream docker registry and not generated by cloudron.

I misread your original comment. I guess you are referring to the cloudron update command of the CLI tool. I thought this was about a cloudron (platform) update. Currently, the focus of the CLI tool is app development and not for end users as such.... So, one can automate what you want already by writing a small script which calls cloudron restore if the update fails.

A temporary workaround: docker stop turn . Some platform updates might turn back the turn service on though (when updating the turn docker image).

@SansGuidon you are absolutely welcome

@nebulon Is there a possibility to pay 50€ or so to push this request? The possibility to use SOGo on a multi-tenant base is really the only thing keeping my stuck in Plesk.

I guess somehow the actual command to move (cutnpaste) the files didn't even reach the server or failed in some auth. Next time, opening the browser inspector should reveal more error details we can work with.

What is your use-case to restore the whole Cloudron from Cloudron itself? I can see if Cloudron and thus the dashboard is not working, a restore might be required, but then it cannot restore itself in such cases.

@humptydumpty this is another great solution.

@marcusquinn not yet, but it is scheduled for next release - https://forum.cloudron.io/topic/9975/what-s-coming-in-9-0-was-8-0 (the "remove global lock for backups" bullet point)

@murgero Thanks, yeah, definitely not doing that now Just looking for the simplest solutions with what we already have. Since the functionality is already there, this is more of an workflow interface feature to just make it available at an earlier stage in the process, and to avoid the additional step and decisions later to do the exact same.

"Thank's" is like.... [image: 1722345022070-90ea0e22-68ef-4c6a-aa8f-2e9dbc9eebe4-image.png]

Indeed, we have space there, so this makes sense to not hide it unnecessarily. Fixed for next release https://git.cloudron.io/cloudron/box/-/commit/44d3baf51aaab4acc3e3a4d5188c38d4dffef257

@humptydumpty Not only on home servers, also OVH and Vultr. Additional files will definitely be with local providers. In this file "50-cloud-init.conf" as it actually is, I simply delete the line

@jdaviescoates currently, those behemoths are not on OIDC yet... But nextcloud has already been ported to OIDC. Just needs a lots of testing

Is it maybe possible to change the order in which incoming mails are filtered? With sieve you can tell the server to discard mails that match certain criteria, but that only works for mails that have not already been classified as SPAM. i suspect this is not that trivial though because the sieve filters work at the mailbox level.