@msbt It's intentional that only superadmins can see it. It won't be good for privacy if an admin could see all the emails being sent. It's OK for superadmins to see this because it's assumed they have SSH access. I have added a note in https://docs.cloudron.io/email/#event-log and fixed the UI to hide the button for non-superadmins.

@mdreira It should clean them up.

@Gary-Host Thanks. So to be clearer here about the update logs. First, tail the log file /home/yellowtent/platformdata/logs/box.log Now, start the update in the UI You will see something like this in the logs: 2022-03-17T05:30:00.012Z box:tasks startTask - starting task 3970 with options {}. logs at /home/yellowtent/platformdata/logs/tasks/3970.log 2022-03-17T05:30:00.012Z box:shell startTask spawn: /usr/bin/sudo -S -E /home/yellowtent/box/src/scripts/starttask.sh 3970 /home/yellowtent/platformdata/logs/tasks/3970.log 0 400 Now, you can check the log file as listed above at /home/yellowtent/platformdata/logs/tasks/3970.log That should give us info on why it's not updating.

Is this bare metal? One way would be a second NIC + passing it to a separate VM for other things. Effectively then you have "two computers" in one.

@girish said in How can I setup a 302 or 301 redirect from a subdomain to an external site?: I am probably missing something. Support for multi domain/aliases is already in Cloudron 7. [image: 1642014209908-36396f8d-fc12-4a8c-a545-d0b4269895b8-image-resized.png] @toxicdorito What is the version of your Cloudron ? The latest lamp package already has support for aliases - What if we want to create an alias or redirect for our dashboard domain? I want https://my.ud.coop to redirect to https://my.uniteddiversity.coop, see https://forum.cloudron.io/post/44785

ok, if you do not have a static IPv4 allocated by Att, then please look into https://docs.cloudron.io/networking/#dynamic-dns and use a domain backend which is programmable (anything besides wildcard and manual) Once that is configured, you can sync dns and your issues should be solved. Further please note the port limitations on such ISP connections https://docs.cloudron.io/email/#smtp-status nearly always is outbound port 25 blocked on such connections, so you most likely have to use some email relay.

@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).