Installation on Contabo VPS:

1. Fresh installed server with Ubuntu 22.04
2. Enable IPv6 as root

enable_ipv6

3. Follow the Cloudron installation

wget https://cloudron.io/cloudron-setup
chmod +x ./cloudron-setup
./cloudron-setup

4. Reboot the server

Sources:
2. https://contabo.com/blog/de/ipv6-auf-ihrem-server-einrichten/
3. https://www.cloudron.io/get.html

on contabo, ipv6 is disabled in the kernel. This should not be needed but this is the default. Unbound fails to start when control port is enabled on a non ipv6 server.

There is a bug in unbound on Ubuntu 22 that it listens on the control interface (port 8953) by default. I have reported the issue on the unbound mailing list, let's see what they say.

But @cilleyperson didn't seem to have the issue with a vanilla install of Ubuntu 22, only on Contabo's version of it, no?

• Setup Contabo account with the instance(s) of your choosing (I am using the VPS L size)
• Add on custom image storage for your Contabo account (at the time of writing this was $1.49 extra per month for 25 GB of image sotorage
• Follow the instructions to download the standard Ubuntu server image to your Contabo custom image storage (at the time of writing this was version 22.04.1)
• Make sure your Contabo VPS has cloud-init enabled so that you can use the custom image
• Go through the Contabo re-install process for your VPS selecting the custom image for the OS
• Follow the instructions to enable VNC viewer access to your Contabo VPS instance so that you can complete the Ubuntu install
• Go through the standard Ubuntu install process using the VNC viewer connection
• I would recommend using the logical volume option to handle your hard disk creation and then edit the logical volume group at installation to use the full amount of disk space available.
• Make sure you enable the SSH server so that you do not need to leave VNC access enables since this is a security issue
• Once Ubuntu is installed, reboot your server, disable VNC access, and go through the rest of the steps using an SSH connection
• I would recommend using a certificate for your SSH connections if possible, it is safer than having SSH exposed with only password authentication on the internet.
• Follow the Cloudron installation instructions to pull down the latest version and complete the setup process on your server.

I'll working on making a more detailed tutorial in the coming weeks, but this should get someone headed in the right direction if they are in the same situation I was.

I may turn this whole experience into a how-to in the future so people can learn from what I did to get this working.

Yes, please do!

I think their German locations run on 100% hydro power (although this is not at all clear - I've asked them multiple times and am struggling to get a definitive answer, and have received conflicting answers from their email support vs social media) so I'm thinking of giving them a try (actually already bought 250gb of object storage from them in a recent sale)

So it looks like while it is a bit more work on Contabo, and you need to pay the small monthly fee for custom OS image hosting, everything does work pretty well.

I may turn this whole experience into a how-to in the future so people can learn from what I did to get this working.

Not sure if the system recognized my complete allotment of RAM and disk space though. Going to need to see what is happening there.

It seems like this all has something to do with the IPv6 settings with the VM but I can't be sure. I wish I knew what others have done in the past to get Cloudron working on Contabo.

Digital Ocean is getting too expensive in terms of monthly costs for me as an individual to run my apps on the platform, so Contabo looked like the best way to solve for that challenge. Unfortunately it seems like there is something fundamentally different about their Ubuntu images causing the Cloudron installer to fail.

https://linuxconfig.org/how-to-disable-ipv6-address-on-ubuntu-22-04-lts-jammy-jellyfish

I think it may have actually caused more issues than it resolved as I received a dpkg error for the nginx install this time, which was new.

I am at a loss in terms of where to go from here. I am using the base Contabo Ubuntu 22.04 install. Seems like it shouldn't be causing this many issues out of the box.

ss -lptn 'sport = :8953'
State           Recv-Q           Send-Q                      Local Address:Port                       Peer Address:Port           Process

So it doesn't look like there is anything running on that port.

I honestly don't need ipv6 on these hosts. Is there a best practice to disable this on Ubuntu 22.04?

Thanks!

Also maybe it can only not bind to port for ipv6? Is ipv6 enabled on that instance?

Dec 09 14:27:15 vmi1119358.contaboserver.net unbound[19504]: [1670596035] unbound[19504:0] error: can't bind socket: Cannot assign requested addres>
Dec 09 14:27:15 vmi1119358.contaboserver.net unbound[19504]: [1670596035] unbound[19504:0] error: cannot open control interface ::1 8953
Dec 09 14:27:15 vmi1119358.contaboserver.net unbound[19504]: [1670596035] unbound[19504:0] fatal error: could not open ports
Dec 09 14:27:15 vmi1119358.contaboserver.net systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE

So now port 8953 is the one that cannot be bound. Very strange. Is there anything else that people know about that is unique to Contabo that my be causing this? I also have the ability to upload custom iso images. Is there an ISO image for cloudron that I could use right out of the gate?

Thanks!

But, the setup script already has code to disable bind9. I am wondering why that doesn't work. Can you please try:

systemctl stop bind9
systemctl disable bind9

Does the above work?