Please send an email to support@cloudron.io with the email address you have registered at git.cloudron.io and I will deactivate the 2fa for that one.

@d19dotca That is strange, we will do a bit more testing here (I think atleast one thing to help us narrow this down is you use encrypted backups)

Thanks, investigating this. I suspect the node module is unable to parse the output because of something in the output. I will keep you posted here.

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?

@girish Oh okay, thank you! My next question was going to be about deleting the snapshot folder, but it was already answered. I appreciate it!

I can reproduce this. Fixed in https://git.cloudron.io/cloudron/box/commit/7cbe60a484cf03c9373c8f57307ad0d9b49a695a . It's a simple change, in case you want apply it locally on your cloudron

@rfg Agree that Cloudron should not accept emails from spoofed sources. We do have code and configuration in place to block this. Let me investigate.

I have added information here on how to change the graph driver using a systemd drop-in - https://cloudron.io/documentation/storage/#docker-image-location . Please use it at your own risk, since as mentioned, we haven't tested with other graph drivers.

@homo for the easiest experience, i would sign up at https://www.digitalocean.com/ . Cloudron is available as a 1-click image in the marketplace. So, you don't have to install it at all.

@necrevistonnezr Thanks, good to know. Will keep an eye for the ubuntu update. Cloudron is not at risk because we only use it internally (it is not exposed via public port). We also don't use NOTIFY query (this is a zone change notification across dns servers) as we use unbound as a recursive resolver and nothing more.

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.

Ah, that did it. Thank you!

Thanks for the answer!

This has been fixed now with https://git.cloudron.io/cloudron/box/commit/2bde023d4dc783761553a0a7be88650e5885b4ad and should be part of the next release.

@msbt d'oh! That worked, I was able to delete the app successfully after manually (and with sudo) deleting the contents of that directory. @girish that directory contained an empty data directory and that's it. Hope that helps debugging!

@PRajShar To clarify what this error is trying to say: Let's assume that you have an existing website app (i.e external to Cloudron) on app.domain.com. Now, you go to Cloudron and try to install an app in the domain app.domain.com. Cloudron will detect that the DNS already has an entry for this and fail with the above error. To fix this, go to your DNS provider and remove the app.domain.com entry. Then in Cloudron, click the Repair (wrench icon) and it should work. Alternately, just use another subdomain app2.domain.com or something.

@subven Have you read https://docs.microsoft.com/en-us/office365/securitycompliance/use-the-delist-portal-to-remove-yourself-from-the-office-365-blocked-senders-lis ? You should be able to get your specific IP delisted.

Yes, the post @d19dotca linked will have the explanation.

Yes it also shows email storage details