@girish Thanks Girish. I assume that'll be fixed in the next bug-fix release as it looks fixed already in the code from this bug report (referencing for others): https://git.cloudron.io/cloudron/dashboard/-/commit/b62da8ba70dd8b4a8964de5a2c01e6ff7afa0e99

That took a while but we are back in business - https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

@vladimir-d said in LDAP not exposing outside: Also I noticed that if I save Directory Server configuration several times, multiple duplicate rules added to iptables: I was able to reproduce this, thanks for reporting. It's fixed in the next release - https://git.cloudron.io/cloudron/box/-/commit/d13905377c375823e7b6fd66bd248421544a1d2c . The duplicate rules are harmless nevertheless.

@WaffleUncle So you are using the Import button in the app section, correct - https://docs.cloudron.io/backups/#import-app-backup ? In your case, it looks like your backups were in the file system and not external. If that is the case, you have to fill up the 'Import Backup' dialog manually: Upload the backup app_client.xxx.tar.gz to somewhere in the server like /tmp/app_client.xxx.tar.gz. In the import UI, Choose Filesystem Put the path as /tmp/app_client.xxx.tar.gz It should import now.

@girish The issue was fixed with last automatic update. Thank you!

@girish That's awesome, thank you. I was going to do it and post the screenshots here, but paused, not sure if even starting the process would "turn it on" and then what... This is super helpeful.

@JavaCraft Can you post the output of free -m ? To move ahead, you can just edit the line readonly MINIMUM_MEMORY="974" to be something lower in the cloudron-setup script. It's at the top of the file around line 14 and run the setup script again.

@nebulon said in my.cloudron.tld is not accessible: nosudo thank you for eyes and help this is so weird and like you I don't know that option. also; etckeeper as not being initiated on that server, so I'm unable to retrace when that change has been made

This happened to me to, and I had to do a full reboot to get the apps back up.

@Gubindev We don't have a special plan/policy as such, but if you can write to us at support@cloudron.io, we will try to help.

@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