@imc67 in the next release, we will suppress those notifications. it seems to not add much value. in any case, the solution is just to wait since cloudron will try again later. it's not a Cloudron issue, the LE service just goes up/down by nature.
@d19dotca it's not a problem. Just the natue of any service being exposed to the internet. There a bots, misconfigured services, compromised iot devices doing all sorts of things. Nothing to worry.
Generally, I am wary of putting this information for general use (and even in docs) because many things can go wrong . So, please, if you care about the data, don't hesitate to contact us on support@ . We help regardless of the subscription plan.
@austinsonger this may happen if the server is a bit overloaded or if the disk I/O is slow. The latter can be quickly checked with hdparm -Tt /dev/<your-root-disk-partition>.
Otherwise the blog seems to be up and running fine by now?
@nebulon @girish @d19dotca Thank's a lot @d19dotca ! For me is a little bit complex append that command in cronjob and I don't know if Cloudron make some integrity test at boot time to try to check if turn is on or off.
Another solution is to use VPS provided firewall to lock that doors... But as @nebulon wrote, one improvement could be add rate-limiting and/or start that services on demand.
Thank's all for your answer
I've synced the expiration now to 7 days to keep changes low until we have a reason to change it
Instead of making it configurable I would prefer a sensible default, since so far no-one else has complained.
