Cloudron Forum

@girish perfect - that fixed that! now bumping to 7.2 - thanks mate

There's this guide - https://docs.cloudron.io/guides/upgrade-ubuntu-20/ in case you haven't seen it already. Main gotcha is that the mysql server sometimes upgrades and sometimes doesn't. In the end, we want MySQL server 8. Sometimes, it asks you whether you want to remove mysql data. Be sure not to remove it!

The upgrade guides should mostly be identical for upgrading Ubuntu. The Cloudron guide has maybe couple of additional notes/configuration for making sure things are running after upgrade. What error are you hitting when upgrading following either of the docs? I suspect they hit the same error.

@girish Boom! Back up and running 🙂
Well this was a joyous outcome. Thanks a bunch Girish!

@girish I don't know if it was installed before the upgrade, but it wasn't enabled, because unbound managed to run without problem 🤷

I'm not sure how it got there. It was supposed to be a clean Ubuntu 16.04. The only things I installed manually besides cloudron are basically ZSH and screen.

In any case, I marked this as solved, thanks !

To close this, turned out that "libpython3.8" was missing on my newly upgraded 20.04 Hetzner system...therefore I was getting the message "dependency problems prevent configuration of collectd"

@necrevistonnezr Don't upgrade yet, I have a blog post that I will publish later today on how to update. It's a bit different than 16 to 18. That main difference is that the mysql server has to be upgraded as well.

@girish I successfully migrated my Cloudron from one server to another. I followed your directions and updated Cloudron to v 6.0.0 before making my final backup of the old server.

Thank you.

@gml said in SSL error after upgrading to 5.6.0 on ubuntu 16:

That seemed to solve it, even if a server reboot did not solve it. I also got a mail, that this was also visible from other mail-servers (not just from my mail client), as I use DANE for certificate pinning.
Thx girish!

I had the same issue. And the same fix. A reboot didn't work, a service restart did the trick. Thanks!

I am not an expert on AWS, but aren't AWS instances only CPU+RAM ? I thought the disk does not resize. This is for EC2 instances though. Are you using lightsail by any chance?