Thank you, Girish, for diagnosing and solving this bug so quickly! Backups are working again.
If somebody else has this issue and needs to do the patch, you would go to the operating system for your server and find the file there and edit it. Cloudron also have a support tool inside Cloudron which enables you to temporarily grant ssh access to your server, which would let Cloudron's brilliant team patch it for you.
I try to avoid puttting screenshots in our docs because they become obsolete in 6 months. Given the amount of 3rd party services we integrate with, it's impossible for us to track UI changes across all the services. I just link to the docs like in https://docs.cloudron.io/backups/#linode-object-storage
If something is really super popular, I make a "guide" with screenshots.
CSRF token are to prevent request replay attacks. I don't know much about the context here for this app, but if you refresh the page and perform the action again, does it work then or is this somehow related to the app you are trying to add, which reports this?
Thanks. Waiting and refreshing seems to have solved this issue.
@LoudLemur looks like the DNS record was pointing to a Cloudron which didn't have any app installed on that (sub)domain. If a Cloudron server as such just gets deleted, then the DNS records are not automatically cleaned up, since there is nothing running anymore to do that.
@privsec I enabled all modules you were showing in the screenshots but I cannot reproduce the log file issue. Is there anything else you configured? Also can you check via the webterminal what the permissions of the log file in question are?