Cloudron Forum

in my specific case - that was due to decryption key error

The percentage is 100% times the CPU cores. So presumably you have 4 cores, which is then reflected in the percentage.

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

The error doesn't appear anymore. Not sure why (cloudron updated to v8 meanwhile).

The errors remaining are "typical build image errors". Thanks for your support!

Great! Thank you so much for the detailed and helpful answer 🙏

@girish I am just finding this thread. I would suggest adding these options:
{ name: '7 daily, 4 weekly, 3 monthly', value: { keepDaily: 7, keepWeekly: 4, keepMonthly: 3 }},
{ name: '7 daily, 4 weekly, 6 monthly', value: { keepDaily: 7, keepWeekly: 4, keepMonthly: 6 }},

The first option is a common backup cycle (I think) and the second option allows for 3 more months of retention (and is halfway between the first and the current 12 month option).

This topic can be marked as closed. I decided to buy an instance with more memory and it worked well.

@girish Yes, Thunderbird supports WKD.

From the Thunderbird FAQs it is explained like this:

Currently, it will search for published keys using the WKD protocol, and it will search for keys in the keys.openpgp.org keyserver.

Source:
https://support.mozilla.org/en-US/kb/openpgp-thunderbird-howto-and-faq#w_how-do-i-get-the-public-keys-of-my-correspondents

Slightly off-topic, but related:
Provider posteo also offers to publish public Keys via wkd, as described in this FAQ:

https://posteo.de/en/help/easygpg-how-do-i-publish-my-public-pgp-key-in-posteos-key-directory-via-web-key-directory-wkd

@girish thanks! It's working fine now.
This is the reason why I love cloudroun ❤

@nebulon really impressive that it is live already 👌

@nottheend thanks for the update! fixed the title as well.

@nottheend said in Help wanted: Mount EFS in EC2:

My only unfulfilled wish is to exclude the nextcloud data now from the cloudron backup.

You can disable the backup for the app but that is of course living dangerously 🙂

@nebulon Thank you. After checking, it turned out that the issue is about efs not mounted.

It seems to be messed up with security groups and/or network interfaces (eni). Hence closing this threat for now. Need to dig deeper and probably understand the concepts of security groups and eni better in AWS.

Thanks for your help!

Edit: Just realizing that can't set it to 'solved'

@girish perfect! Thank you so much! I really highly appreciate the effort! Thanks! I see it now!