Cloudron Setup on Contabo - VPS L Instances - Ubuntu 22.04 x64
-
@cilleyperson I followed the instructions to disable ipv6 on a fresh 22.04 install but still no luck. I disabled ipv6 using the process shown here:
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.
-
@cilleyperson have you tried to spin up a fresh instance with ipv6 enabled? Possibly this is a contabo side switch, while creating the instance.
-
@nebulon I have tried this on a completely fresh Contabo VPS L instance and the same thing happens, the Unbound service fails, causing the install script to fail in the same manner as what I first reported.
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.
-
@cilleyperson I am going to try one more thing. I am going to use the vanilla Ubuntu ISO as a custom image to install from and try and use that to re-build my VPS with. Maybe that will allow me to bypass whatever is causing this problem.
-
@cilleyperson Ok, so we have success! Turns out, whatever image Contabo uses by default is not something that Cloudron likes at all. I used a custom image with the vanilla 22.04.1 ISO and it works fine.
Not sure if the system recognized my complete allotment of RAM and disk space though. Going to need to see what is happening there.
-
@cilleyperson I've got it! Managed to resize the logical volume to take advantage of all the space on my Contabo VPS.
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.
-
@cilleyperson said in Cloudron Setup on Contabo - VPS L Instances - Ubuntu 22.04 x64:
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)
-
@nebulon One last follow-up for anyone else out there looking at this and trying to install Cloudron on Contabo VPS instances. Here are the steps I went through:
- 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.
-
C cilleyperson has marked this topic as solved on
-
@cilleyperson I signed up with Contabo and created a new server now . I managed to reproduce your installation issue, investigating.
-
G girish has marked this topic as unsolved on
-
-
-
@girish said in Cloudron Setup on Contabo - VPS L Instances - Ubuntu 22.04 x64:
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?
-
@jdaviescoates it's a bit convoluted....
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.
-
Buy me a beer!
Installation on Contabo VPS:
- Fresh installed server with Ubuntu 22.04
- Enable IPv6 as root
enable_ipv6- Follow the Cloudron installation
wget https://cloudron.io/cloudron-setup chmod +x ./cloudron-setup ./cloudron-setup- Reboot the server
Sources:
2. https://contabo.com/blog/de/ipv6-auf-ihrem-server-einrichten/
3. https://www.cloudron.io/get.html -
@jdaviescoates Correct, the vanilla install works fine. It looks like based on what @girish found it can easily be solved by enabling ipv6 in the kernel. Thank you @SirFiChi for posting that process!
-
G girish referenced this topic on
-
This is fixed in 7.3.5 (will be released next week).
-
G girish has marked this topic as solved on
