unbound and network error Cloudron version 9.0.5

[luckow]

First time in history!

Problem is: there is no way to log in to my dashboard.

On one of my instances with 9.0.5 (Ubuntu 24.04.3 LTS) in my home network behind a fritz.box: systemctl --failed produces a

● systemd-networkd-wait-online.service loaded failed failed Wait for Network to be Configured
● unbound-resolvconf.service loaded failed failed Unbound asyncronous resolvconf update helper

Restarting the services produces a No DNS servers specified, refusing operation. and Timeout occurred while waiting for network connectivity.

DNS resolving works:

host www.cloudron.io 127.0.0.53
Using domain server:
Name: 127.0.0.53
Address: 127.0.0.53#53
Aliases:

www.cloudron.io has address 165.227.67.76
www.cloudron.io has IPv6 address 2604:a880:800:10::b66:f001

DNS entry for my.example.org is active and correct. VPN & ssh into the instance is also working.

Any ideas on how to fix this?

[luckow]

Okay, found and fixed.
/etc/netplan/50-cloud-init.yaml was attempting to manage both of my Ethernet ports. One of them is never connected to a network. Once I disabled the second port in YAML and restarted the service, everything worked perfectly.

[nebulon]

kinda looks like networkd from the systemd suite is not able to get to an active state. That job basically checks for overall connectivity of the system and many services like unbound have a dependency on that. So first that systemd-networkd-wait-online.service needs to get up and running. Do you have any more error logs of that one? Given that the one thing you posted was about " No DNS servers specified..." might indicate the system itself has no DNS server. Usually this comes via dhcp (in your case a dhcp answer from the fritzbox) Did you configure anything recently around networking or your fritzbox as such? What DNS servers do you get on other devices behind that fritzbox?

[luckow]

it's complicated.
After installing a pending update on the fritz.box, the my dashboard is working again. systemd ...network and unbound-resolvconf have failed (again). Mmh.

nothing special (?) in the logs:
Subject: Unit process exited - An ExecStart= process belonging to unit systemd-networkd-wait-online.service has exited.
Subject: Unit failed - The unit systemd-networkd-wait-online.service has entered the 'failed' state with result 'exit-code'.
Subject: A start job for unit systemd-networkd-wait-online.service has failed - A start job for unit systemd-networkd-wait-online.service has finished with a failure.

No more DNS server behind fritz.box.
No configuration around networking.

Q: I did a quick check on other Cloudron instances and recognizd ● unbound-resolvconf.service loaded failed failed Unbound asyncronous resolvconf update helper on every instance. Is this "normal"?

[luckow]

Okay, found and fixed.
/etc/netplan/50-cloud-init.yaml was attempting to manage both of my Ethernet ports. One of them is never connected to a network. Once I disabled the second port in YAML and restarted the service, everything worked perfectly.

[nebulon]

Ah glad you got down to the root cause. Do you know why this has suddenly changed on your system? I would have expected to fail also pre Cloudron 9 then if systemd's network state fails.

[luckow]

@nebulon No luck, I don't have a reliable answer for you.