What's coming in Cloudron 7.1

[bubonicfred]

@girish Feel your pain about npm. Was there something new that came up about request? I don't use it directly but use dependencies that do.

[girish]

Final update before the release. Initial, IPv6 support is in - all the DNS backends have been updated to support AAAA records. There is a checkbox in the Network view to enable the IPv6 support.

This is currently "experimental". Currently, there is a lot of complications and unknowns wrt docker's ipv6 support. I will make a separate post about this, but for Cloudron, the initial iteration the plan is to enable IPv6 only for HTTP(S) services. Essentially, the apps will have IPv6 support but not any exposed ports (like say the git port) nor the email server.

[timconsidine]

@girish just wondering about current status of 7.1.0
I needed to move my server and noticed that default install on clean machine is 7.1.0. But in Cloudron it says this release is beta.

I actually installed 7.0.4 on the clean machine, so I could restore from backups. Generally went fine. I then upgraded to 7.1.0 through console.

Seems ok but email status check seems off still.
And System Info shows no data.

[timconsidine]

@timconsidine ah but actually all apps seem stuck in Configuring queued status.

EDIT (1) : they seem progressively to exit this status and become Running

EDIT (2) : System Info now showing some data. But interestingly it seems server was down for a while after upgrade to 7.1 from this chart.

EDIT (3) : 2 apps refuse to enter Running, stuck in Starting ...
They're not critical for now.

So just wondering about 7.1.0

[girish]

7.1 was staged for installation a couple of days back. I would wait before updating though, there is atleast one issue we know of which is now fixed and there will be a 7.1.1. I would not trigger an update on existing installations unless it's not critical (and of course, help us with the testing).

[girish]

@girish said in What's coming in Cloudron 7.1:

Final update before the release. Initial, IPv6 support is in - all the DNS backends have been updated to support AAAA records. There is a checkbox in the Network view to enable the IPv6 support.

This is currently "experimental". Currently, there is a lot of complications and unknowns wrt docker's ipv6 support. I will make a separate post about this, but for Cloudron, the initial iteration the plan is to enable IPv6 only for HTTP(S) services. Essentially, the apps will have IPv6 support but not any exposed ports (like say the git port) nor the email server.

We figured this one out and IPv6 support will be complete in 7.1. It will support export ports and the email server from the get-go! But as mentioned in previous comment, please hold on before updating if your Cloudron instance is critical.

[girish]

@timconsidine said in What's coming in Cloudron 7.1:

@timconsidine ah but actually all apps seem stuck in Configuring queued status.

EDIT (1) : they seem progressively to exit this status and become Running

This is expected. Docker is updated, the internal network is now IPv6 and all app containers are re-created to support IPv6.

EDIT (3) : 2 apps refuse to enter Running, stuck in Starting ...

Can you please tell me which apps these are and what you see in their logs? Sometimes, depending on your server, it could be that they are taking some time to start up.

[timconsidine]

@girish said in What's coming in Cloudron 7.1:

@timconsidine said in What's coming in Cloudron 7.1:

@timconsidine ah but actually all apps seem stuck in Configuring queued status.

EDIT (1) : they seem progressively to exit this status and become Running

This is expected. Docker is updated, the internal network is now IPv6 and all app containers are re-created to support IPv6.

EDIT (3) : 2 apps refuse to enter Running, stuck in Starting ...

Can you please tell me which apps these are and what you see in their logs? Sometimes, depending on your server, it could be that they are taking some time to start up.

Thank you for the offer.
When I reviewed them, I found they were custom package apps.
And I decided I wasn't using them enough, so uninstalled them. Quick solution

[nebulon]

@timconsidine possibly they were using CloudronManifest version 1, which was deprecated for some time now and got removed with 7.1
What this means is, that the injected env vars will now always be prefixed with CLOUDRON_ and maybe your custom apps were still looking for example for MYSQL_HOST instead of CLOUDRON_MYSQL_HOST?

[timconsidine]

@nebulon ah good point, thank you
I will check some other custom apps

[msbt]

@nebulon I still have 2 custom apps running on manifestversion 1, what will happen to them if I upgrade before updating those apps?

[humptydumpty]

@girish said in What's coming in Cloudron 7.1:

7.1 was staged for installation a couple of days back. I would wait before updating though, there is atleast one issue we know of which is now fixed and there will be a 7.1.1. I would not trigger an update on existing installations unless it's not critical (and of course, help us with the testing).

I triggered a manual update check before coming across this post. Is there a way to tell cloudron to skip this update or stop it from auto-updating?

[msbt]

@humptydumpty go to Settings and change the update schedule, in there you can choose to disable automated updates

[avatar1024]

@humptydumpty I believe that updating to 7.1 can only be done manually and will NOT happen through auto update (if with auto update enabled).

[nebulon]

@avatar1024 that is correct, releases which are not yet put out for all users, will not be auto-updated. Our current approach is, to first make a release for new installation and people who would like to manually update to it. Then if things look good, we will slowly roll it out for auto-updates (if enabled on a Cloudron) over around a week or so.

[girish]

@msbt manifest v1 apps won't work anymore in 7.1. i.e it will just not start properly. Note that just bumping the manifestVersion to 2 and changing the env variables to CLOUDRON_ is all that is needed, nothing else.

[imc67]

@girish said in What's coming in Cloudron 7.1:

@girish said in What's coming in Cloudron 7.1:

Final update before the release. Initial, IPv6 support is in - all the DNS backends have been updated to support AAAA records. There is a checkbox in the Network view to enable the IPv6 support.

This is currently "experimental". Currently, there is a lot of complications and unknowns wrt docker's ipv6 support. I will make a separate post about this, but for Cloudron, the initial iteration the plan is to enable IPv6 only for HTTP(S) services. Essentially, the apps will have IPv6 support but not any exposed ports (like say the git port) nor the email server.

We figured this one out and IPv6 support will be complete in 7.1. It will support export ports and the email server from the get-go! But as mentioned in previous comment, please hold on before updating if your Cloudron instance is critical.

Just updated to 7.1.2 I noticed I had to 'save location' of the apps to add the AAAA records. However the mailserver and Cloudron access URL still don't have AAAA records, not even after restarting the mailserver. Is this expected?

[girish]

@imc67 you have to go to Domains -> Sync DNS records for the existing apps/mail server.

Before you suggest it, yes, we should probably do this when IPv6 is enabled As a heads up, there is also a quirk that if you disable IPv6, the AAAA records are not removed by the sync .

[micmc]

@girish said in What's coming in Cloudron 7.1:

@girish said in What's coming in Cloudron 7.1:

We figured this one out and IPv6 support will be complete in 7.1. It will support export ports and the email server from the get-go! But as mentioned in previous comment, please hold on before updating if your Cloudron instance is critical.

AMAZING WORK! From our exceptional professional and cutting edge team of developers at Cloudron, should it be said once in a while.

Thanks for your fantastic work @girish @nebulon guys you are simply the bests.

[girish]

Cloudron 7.1 is now available to all. Locking this thread.