@humptydumpty
A heads up for everyone worldwide --- Privacy.com is for US residents only
https://privacy.com/signup

@robi Yep, much better, thank you!

This is to do with the manifest changes in 7.1. Cloudron manifest v1 is not supported anymore in 7.1. The main change from manifest v1 to v2 is that env variables have the CLOUDRON_ prefix.

manifest v2 was added ~3 years ago in Cloudron 4.1

@nj Cloudro relies on Ubuntu LTS versions and security updates are enabled automatically (independent from Cloudron releases). So once the ubuntu securty team updates the kernels, all Cloudrons will get is as well. Since this is a kernel issue, you will likely see some "reboot required" notification in your Cloudron dashboard afterwards.

@scooke the solution was in advanced settings creating let's encrypt manually at least this is what I understood from my friend.

@grimm1369 Let's continue this further at https://forum.cloudron.io/post/44414

@PlaceToGame hi there, you would have to start fresh with a pristine Ubuntu image/installation. This is to avoid any side-effects from half-installed services.

@girish Thanks for your help, I was able to solve everything without erasing the entire system, excellent and quick solution.

I have not documented the notification rest api at: https://docs.cloudron.io/api.html#tag/Notifications

@girish Sounds great, thanks Girish.

@yusf it should be safe now, can you please try (but we still have to show that banner because we are rolling out in batches).

@msbt thanks for the report. This is fixed now, but will only make it into the next release or patch release.

@imkidcable said in demo.cloudron.io is down?:

I've heard that Hetzner is a great alternative, so maybe consider giving them a try.

yes, we are hetzner customers too! We try to spread our services across many provides, just for reliability reasons. But true, sometimes they have some very nice deals, let me check.

@Olgoonik-IT thanks for reporting, I have fixed this now.

@imc67 essentially the patch for this is https://git.cloudron.io/cloudron/box/-/commit/eb0662b2455e0687ab3ce5dd02d2466e16670092 so two files need to be adjusted. The .ejs file is a template which will result in /etc/nginx/applications/my.<domain.com>.conf so besides the editing the .ejs file additionally edit that file and then systemctl restart nginx and systemctl restart box.

@LeeW Thanks for trying it and letting us know!

@nebulon I didn't get any notifications in the dashboard for OOM which is why debugging was fairly unintuitive.

@girish If I encounter it again, I'll check dmesg and let you know.

@nebulon Unfortunatelly not.