What's coming in 5.6

[d19dotca]

@girish Dang, that's too bad. Thank you for confirming though. I'll keep that process in mind as something I can do when the time comes then (which I suspect will be in about 2 months or earlier), but hoping there'll be an easier way to still have the box data on the local disk rather than needing to move it in its entirety to a new disk. Just as how the app locations can be changed and it automatically moves the data, it'd be great if Cloudron could do that part too without needing a manual intervention for it. Plus it'd save a little bit of cost to the admin as they wouldn't need to create such a large external disk for it all, just for the emails.

[girish]

The 5.6 pre-release is out. Only update if you are truly eager. We will roll this update out very slowly over this week and the next.

If you hit any issues, please do open separate threads. The docs are still getting fixed up, so let me know if you find something hard to follow.

[mehdi]

@girish said in What's coming in 5.6:

• Add a way to whitelist inbound ports. This will help apps like netdata, snmp monitors and other monitoring "agents".
• Add flag in manifest for reverse proxying to a port (for the OLS app).

Could I have more detail about these 2 features ? They look quite interesting !

[girish]

@mehdi said in What's coming in 5.6:

Add a way to whitelist inbound ports. This will help apps like netdata, snmp monitors and other monitoring "agents".

https://docs.cloudron.io/networking/#whitelist-ports

As for the port proxying, it didn't make it to this release. It was meant for the OLS app that @MooCloud_Matt packaged. We have to try it for the next release.

[d19dotca]

@girish I just updated to 5.6.0 to test it out. Looks great so far! Only thing I'd suggest changing or fixing is the Max Message Size on the Email page, as it's default at 25 MB but when I go to change it, it goes in weird 10 MB intervals from 1 MB, so it's 21 MB, 31 MB, 41 MB, etc which are strange numbers to use. I'd suggest it either be configurable (i.e. a text box) or if it's on a slider then it should go up in 1 MB increments rather than 10 + 1.

[girish]

@d19dotca Ah thanks, I can reproduce this easily. Strange

Edit: I have fixed this for next release.

[imc67]

Update to 5.6 failed with error but seems to work anyway.

Log:

Sep 12 09:34:03 box:tasks 4283: {"percent":70,"message":"Installing update"}
Sep 12 09:34:03 box:shell update spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/update.sh /tmp/box-2509650539
Sep 12 09:34:03 box:shell update (stdout): Updating Cloudron with /tmp/box-2509650539
Sep 12 09:34:03 box:shell update (stdout): => reset service cloudron-updater status in case it failed
Sep 12 09:34:03 box:shell update (stdout): Failed to reset failed state of unit cloudron-updater.service: Unit cloudron-updater.service is not loaded.
Sep 12 09:34:03 box:shell update (stdout): => Run installer.sh as cloudron-updater.
Sep 12 09:34:03 box:shell update (stdout): => starting service (ubuntu 18.04) cloudron-updater. see logs at /home/yellowtent/platformdata/logs/updater/cloudron-updater-2020-09-12_07-34-03.log
Sep 12 09:34:03 box:shell update (stdout): Running as unit: cloudron-updater.service
Sep 12 09:34:03 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds
Sep 12 09:34:08 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds
Sep 12 09:34:13 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds
Sep 12 09:34:18 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds
Sep 12 09:34:23 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds
Sep 12 09:34:28 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds

[girish]

@imc67 are you referring to "Failed to reset failed state"? That message can be ignored.

[imc67]

@girish it was another error message but forgot to take a screenshot. It was something like “Cloudron couldn’t start” with a link to the log.

[imc67]

@girish my Cloudron #3 also got the same error, this time with screenshot and log:

Log:

Sep 12 23:44:27 box:tasks 2022: {"percent":70,"message":"Installing update"}
Sep 12 23:44:27 box:shell update spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/update.sh /tmp/box-1847933296
Sep 12 23:44:27 box:shell update (stdout): Updating Cloudron with /tmp/box-1847933296
Sep 12 23:44:27 box:shell update (stdout): => reset service cloudron-updater status in case it failed
Sep 12 23:44:27 box:shell update (stdout): Failed to reset failed state of unit cloudron-updater.service: Unit cloudron-updater.service is not loaded.
Sep 12 23:44:27 box:shell update (stdout): => Run installer.sh as cloudron-updater.
Sep 12 23:44:27 box:shell update (stdout): => starting service (ubuntu 18.04) cloudron-updater. see logs at /home/yellowtent/platformdata/logs/updater/cloudron-updater-2020-09-12_21-44-27.log
Sep 12 23:44:27 box:shell update (stdout): Running as unit: cloudron-updater.service
Sep 12 23:44:27 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds
Sep 12 23:44:32 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds
Sep 12 23:44:37 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds
Sep 12 23:44:42 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds
Sep 12 23:44:47 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds
Sep 12 23:44:52 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds

[girish]

@imc67 can you see what the error is in /home/yellowtent/platformdata/logs/updater/cloudron-updater-2020-09-12_21-44-27.log ?

[imc67]

@girish I've sent you the log file via email

[girish]

There is a SOGo regression in 5.6 . https://forum.cloudron.io/topic/3161/sogo-connectivity-issue-with-cloudron-5-6 has the bug report and workaround.