Upgrade to Ubuntu 24.04 - Share your experience!

[NCKNE]

Updated to Cloudron 8.0 without any issues and then to Ubuntu 24.04.
I was facing DNS lookup errors in the mail logs and had to add
interface 127.0.0.1
to the cloudron unbound config.
Everything working smoothly since then.

[girish]

@NCKNE said in Upgrade to Ubuntu 24.04 - Share your experience!:

I was facing DNS lookup errors in the mail logs and had to add
interface 127.0.0.1

Thanks for the feedback but where did you have to add this?

[necrevistonnezr]

@NCKNE said in Upgrade to Ubuntu 24.04 - Share your experience!:

to the cloudron unbound config.

[necrevistonnezr]

BTW, does make more sense to check & modify /etc/default/collectd before upgrading?

[girish]

@NCKNE said in Upgrade to Ubuntu 24.04 - Share your experience!:

I was facing DNS lookup errors in the mail logs and had to add
interface 127.0.0.1
to the cloudron unbound config.

mm, no. In Cloudron 8, unbound runs of 127.0.0.150 . Your unbound config should look like this:

root@my:~# cat /etc/unbound/unbound.conf.d/cloudron-network.conf 
# Unbound is used primarily for RBL queries (host 2.0.0.127.zen.spamhaus.org)
# We cannot use dnsmasq because it is not a recursive resolver and defaults to the value in the interfaces file (which is Google DNS!)

server:
        port: 53
        interface: 127.0.0.150
        interface: 172.18.0.1
        ip-freebind: yes
        do-ip6: yes
        access-control: 127.0.0.1 allow
        access-control: 172.18.0.1/16 allow
        cache-max-negative-ttl: 30
        cache-max-ttl: 300
        # enable below for logging to journalctl -u unbound
        # verbosity: 5
        # log-queries: yes

# https://github.com/NLnetLabs/unbound/issues/806
remote-control:
    control-enable: no

If you docker inspect mail you will see it uses 172.18.0.1 as the DNS server (which you see as interface above).

127.0.0.53 is the systemd-resolved and it uses whatever your DHCP/network or VM provides by default.

In fact, there is nothing on 127.0.0.1 ... unless of course you have some custom configuration in your network.

[jdaviescoates]

@necrevistonnezr I pretty much never do upgrades, I tend to just spin up a competely new updated server and then migrate my Cloudron to it.

[necrevistonnezr]

I dove in yesterday with actually zero problems on my home server….

[IniBudi]

Already upgraded tp 24.04 and there's no problem with Cloudron 8.0 🥳

[scurtis]

I upgraded to Cloudron 8.0 on Ubuntu 22.04 and on reboot had OIDC errors on all apps that were using Cloudron login for some reason. Everything else was working fine though.

I spun up a clean Ubuntu 24.04 machine, installed Cloudron 8 clean and then reinstalled each app from its backup and they all worked.

I considered this a good test of backup / restore anyway but not sure why i was getting authentication errors. I still have the partial broken VM shutdown and now using new VM so all is fine.

[nebulon]

Did you run the cloudron-support --troubleshooting command on that broken Cloudron to get some overview of what might have gone wrong?

[adhodgson]

I was looking at setting up an AdguardHome instance but wanted it to use the recursive Unbound DNS server as upstream rather than a third-party DNS server like Google or CloudFlare. Some questions on the Unbound config:

Unbound is used primarily for RBL queries (host 2.0.0.127.zen.spamhaus.org)

We cannot use dnsmasq because it is not a recursive resolver and defaults to the value in the interfaces file (which is Google DNS!)

In my case Unbound is using Hetzner DNS servers based on Netplan config. Should Cloudron use Google DNS by default?

server:
port: 53
interface: 127.0.0.150
interface: 172.18.0.1

Does this mean that in Adguard Home I can use 172.18.0.1 as the upstream DNS server?

[...]

    cache-max-negative-ttl: 30
    cache-max-ttl: 300

Though these options may make this unviable.

Thanks.
Andrew.

[girish]

@adhodgson no, do not use Cloudron's unbound as the resolver for AdGuard, that is just asking for trouble. unbound is mostly an internal implementation detail from Cloudron point of view. In Cloudron 8, it's role has decreased a lot. In future, we will most likely completely remove it. It's best to use some other resolver on your network.