Ubuntu 22 installation fail
-
@girish I am trying to install Cloudron on a fresh Ubuntu 22.04 installation and the installation process stops and does not complete.
==> Disable temporary address (IPv6) # Disable exim4 (1blu.de) systemctl stop exim4 || true Failed to stop exim4.service: Unit exim4.service not loaded. systemctl disable exim4 || true Failed to disable unit: Unit file exim4.service does not exist. # Disable bind for good measure (on online.net, kimsufi servers these are pre-installed) systemctl stop bind9 || true Failed to stop bind9.service: Unit bind9.service not loaded. systemctl disable bind9 || true Failed to disable unit: Unit file bind9.service does not exist. # on ovh images dnsmasq seems to run by default systemctl stop dnsmasq || true Failed to stop dnsmasq.service: Unit dnsmasq.service not loaded. systemctl disable dnsmasq || true Failed to disable unit: Unit file dnsmasq.service does not exist. # on ssdnodes postfix seems to run by default systemctl stop postfix || true Failed to stop postfix.service: Unit postfix.service not loaded. systemctl disable postfix || true Failed to disable unit: Unit file postfix.service does not exist. # on ubuntu 18.04 and 20.04, this is the default. this requires resolvconf for DNS to work further after the disable systemctl stop systemd-resolved || true systemctl disable systemd-resolved || true Removed /etc/systemd/system/multi-user.target.wants/systemd-resolved.service. Removed /etc/systemd/system/dbus-org.freedesktop.resolve1.service. # on vultr, ufw is enabled by default. we have our own firewall ufw disable || true Firewall stopped and disabled on system startup # 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.
root@vmiXXXXXXX:~# systemctl status unbound.service × unbound.service - Unbound DNS server Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-11-29 11:03:22 UTC; 3min 16s ago Docs: man:unbound(8) Process: 19575 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=0/SUCCESS) Process: 19578 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=0/SUCCESS) Process: 19581 ExecStart=/usr/sbin/unbound -d -p $DAEMON_OPTS (code=exited, status=1/FAILURE) Process: 19582 ExecStopPost=/usr/lib/unbound/package-helper chroot_teardown (code=exited, status=0/SUCCESS) Main PID: 19581 (code=exited, status=1/FAILURE) CPU: 25ms Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: Stopped Unbound DNS server. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: unbound.service: Start request repeated too quickly. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: unbound.service: Failed with result 'exit-code'. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: Failed to start Unbound DNS server.
root@vmiXXXXXXX:~# journalctl -xeu unbound.service ░░ The job identifier is 2706 and the job result is failed. Nov 29 11:03:21 vmiXXXXXXX.contaboserver.net systemd[1]: unbound.service: Scheduled restart job, restart counter is at 4. ░░ Subject: Automatic restarting of a unit has been scheduled ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ Automatic restarting of the unit unbound.service has been scheduled, as the result for ░░ the configured Restart= setting for the unit. Nov 29 11:03:21 vmiXXXXXXX.contaboserver.net systemd[1]: Stopped Unbound DNS server. ░░ Subject: A stop job for unit unbound.service has finished ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A stop job for unit unbound.service has finished. ░░ ░░ The job identifier is 2849 and the job result is done. Nov 29 11:03:21 vmiXXXXXXX.contaboserver.net systemd[1]: Starting Unbound DNS server... ░░ Subject: A start job for unit unbound.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit unbound.service has begun execution. ░░ ░░ The job identifier is 2849. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net unbound[19581]: [1669719802] unbound[19581:0] error: can't bind socket: Cannot assign requested address for ::1 port 8953 Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net unbound[19581]: [1669719802] unbound[19581:0] error: cannot open control interface ::1 8953 Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net unbound[19581]: [1669719802] unbound[19581:0] fatal error: could not open ports Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit unbound.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: unbound.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: Failed to start Unbound DNS server. ░░ Subject: A start job for unit unbound.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit unbound.service has finished with a failure. ░░ ░░ The job identifier is 2849 and the job result is failed. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5. ░░ Subject: Automatic restarting of a unit has been scheduled ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ Automatic restarting of the unit unbound.service has been scheduled, as the result for ░░ the configured Restart= setting for the unit. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: Stopped Unbound DNS server. ░░ Subject: A stop job for unit unbound.service has finished ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A stop job for unit unbound.service has finished. ░░ ░░ The job identifier is 2992 and the job result is done. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: unbound.service: Start request repeated too quickly. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: unbound.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'. Nov 29 11:03:22 vmiXXXXXXX.contaboserver.net systemd[1]: Failed to start Unbound DNS server. ░░ Subject: A start job for unit unbound.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit unbound.service has finished with a failure. ░░ ░░ The job identifier is 2992 and the job result is failed.
-
@girish No, not work
root@vmiXXXXXXX:~# curl https://ipv6.api.cloudron.io/api/v1/helper/public_ip curl: (7) Couldn't connect to server
But in a testing instance of Oracle,
curl https://ipv6.api.cloudron.io/api/v1/helper/public_ip
is not working either and is installing Cloudron without any problem