Solved Installing Cloudron, Unbound exited with error

[alwynispat]

I've tried installing Cloudron multiple times but keep getting stuck at the same spot. Unbound service was not able to successfully start.
Followed the guide here didnt help, https://docs.cloudron.io/troubleshooting/
I'm on Ubuntu 20.04, trying to install Cloudron 7.3.4 using ./cloudron-setup, Ubuntu is a VM on my Windows 10 host using Hyper-V.

× unbound.service - Unbound DNS server
     Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2022-12-22 04:44:11 UTC; 5min ago
       Docs: man:unbound(8)
   Main PID: 7130 (code=exited, status=1/FAILURE)
        CPU: 10ms

Dec 22 04:44:10 sgpvm01 systemd[1]: unbound.service: Failed with result 'exit-code'.
Dec 22 04:44:10 sgpvm01 systemd[1]: Failed to start Unbound DNS server.
Dec 22 04:44:11 sgpvm01 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Dec 22 04:44:11 sgpvm01 systemd[1]: Stopped Unbound DNS server.
Dec 22 04:44:11 sgpvm01 systemd[1]: unbound.service: Start request repeated too quickly.
Dec 22 04:44:11 sgpvm01 systemd[1]: unbound.service: Failed with result 'exit-code'.
Dec 22 04:44:11 sgpvm01 systemd[1]: Failed to start Unbound DNS server.

Install logs

Setting up unbound (1.13.1-1ubuntu5.3) ...
Created symlink /etc/systemd/system/multi-user.target.wants/unbound.service → /lib/systemd/system/unbound.service.
Created symlink /etc/systemd/system/unbound.service.wants/unbound-resolvconf.service → /lib/systemd/system/unbound-resolvconf.service.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.
Job for unbound.service failed because the control process exited with error code.
See "systemctl status unbound.service" and "journalctl -xeu unbound.service" for details.
invoke-rc.d: initscript unbound, action "start" failed.
● unbound.service - Unbound DNS server
     Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2022-12-22 04:43:46 UTC; 4ms ago
       Docs: man:unbound(8)
    Process: 4603 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=0/SUCCESS)
    Process: 4606 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=0/SUCCESS)
    Process: 4609 ExecStart=/usr/sbin/unbound -d -p $DAEMON_OPTS (code=exited, status=1/FAILURE)
    Process: 4610 ExecStopPost=/usr/lib/unbound/package-helper chroot_teardown (code=exited, status=0/SUCCESS)
   Main PID: 4609 (code=exited, status=1/FAILURE)
        CPU: 9ms

Dec 22 04:43:46 sgpvm01 systemd[1]: unbound.service: Failed with result 'exit-code'.
Dec 22 04:43:46 sgpvm01 systemd[1]: Failed to start Unbound DNS server.

# we need unbound to work as this is required for installer.sh to do any DNS requests
echo -e "server:\n\tinterface: 127.0.0.1\n" > /etc/unbound/unbound.conf.d/cloudron-network.conf
systemctl restart unbound
Job for unbound.service failed because the control process exited with error code.
See "systemctl status unbound.service" and "journalctl -xeu unbound.service" for details.

[murgero]

@alwynispat Sounds like there is something else taking port 53(?I think?) you should see what service is running on that port and stop it and reinstall cloudron

[subven]

Take a look at this thread. There is lots of informations and possible fixes for that kind of problem in there

[jdaviescoates]

@alwynispat said in Installing Cloudron, Unbound exited with error:

Ubuntu is a VM on my Windows 10 host using Hyper-V.

I don't know enough to know, but perhaps that isn't supported.

[girish]

Think this is related to https://forum.cloudron.io/topic/8171/cloudron-setup-on-contabo-vps-l-instances-ubuntu-22-04-x64/ . @alwynispat I guess the server does not have IPv6 ?

[girish]

OK, I have fixed the unbound issue with IPv6. It's an upstream bug but I have made a workaround for the moment. Fix will be part of 7.3.5 (released next week).