Cloudron 3.3 released

[girish]

Cloudron 3.3 is now available for all. You can read more in our blog post.

Highlights:

• Ubuntu 18.04 Support
• Cloudflare HTTP Proxy Support
• Exoscale SOS backup regions
• New events for domains, certs, mailbox activities
• Dynamic DNS

[girish]

Instructions on how to upgrade to Ubuntu 18.04 is here - https://cloudron.io/blog/2018-11-26-upgrading-to-bionic.html

[necrevistonnezr]

@girish
The instructions read

Accept running an additional ssh deamon at port 1022

I think it's therefore necessary to execute

iptables -I INPUT -p tcp --dport 1022 -j ACCEPT

before running the upgrade as suggested by the Ubuntu release updater, since Cloudron blocks this port via iptable by default (?).

[necrevistonnezr]

Otherwise, the instructions worked great. Just updated my homeserver over SSH from 16.0.4 to 18.0.4.

Thanks!

[ahelton]

@girish How do I update to 3.3? I login to Cloudron and go to Setting and click 'Check for Updates' and nothing happens...? I'm still running 3.2.3 as seen below:

[girish]

@ahelton Do you have wallabag or owncloud installed? If so, the update is not available is not available if those apps are installed since the upstream apps are still adding support for newer database versions.

[ahelton]

@girish I have Wallabag installed, so that explains it. Thanks.

[girish]

@ahelton Upstream wallabag is close to fixing the issue. You can track it at https://github.com/wallabag/wallabag/pull/3758

[saglagla]

I've seen that the isssue was merged. The update will be deployed soon ?
Still in 3.2.3 @girish

[girish]

@saglagla https://github.com/wallabag/wallabag/issues/3739 also needs to be fixed. It looks like only wallabag 3.4 will support it.

[ahelton]

Thanks for keeping us posted, @girish . Will just have to wait for Wallabag 3.4!

[saglagla]

@girish said in Cloudron 3.3 released:

@saglagla https://github.com/wallabag/wallabag/issues/3739 also needs to be fixed. It looks like only wallabag 3.4 will support it.

But that's mean there is some issue to migrate only ?
If I backup Wallabag, destroy it. Upgrade and then re-install, it will work ?

Or there is an issue between wallabag and cloudron > 3.2.3 ?

[nebulon]

@saglagla the issue is the Postgresql version. The current wallabag is not yet compatible with the version of Postgres Cloudron > 3.2.3 ships. So reinstallation would not work. This is the reason we block the Cloudron update for instances which have wallabag installed.

[jk]

@nebulon said in Cloudron 3.3 released:

(...) The current wallabag is not yet compatible with the version of Postgres Cloudron > 3.2.3 ships. So reinstallation would not work. This is the reason we block the Cloudron update for instances which have wallabag installed.

It looks like making Wallabag support a newer version of Postgresql is literally a single-line patch.

Might it make sense to carry this as a custom patch for now and be done with it?

[iamthefij]

Looks like the patch that @jk referred to has been merged into Wallabag for 2.4, it would be nice to have this patched in the Cloudron version.

I've submitted a Merge Request for the wallabag-app here: https://git.cloudron.io/cloudron/wallabag-app/merge_requests/1

Is it possible to get this merged so that we can upgrade Cloudron?

[girish]

I think I managed to get it work using the 2.4 branch. Tracking this at https://git.cloudron.io/cloudron/wallabag-app/issues/10

[jk]

Thanks a lot!