Cloudron Setup on Contabo - VPS L Instances - Ubuntu 22.04 x64
-
@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.
-
G girish has marked this topic as unsolved on
-
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.
@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?
-
@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.
-
Wow. I had cloudron running on Ubuntu 18.04, backuped the server last night and tried four times to install coudron now.
Bad luck. I first tought about doing it in the holidays, but now I stuck with a disabled 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 -
@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 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
-
G girish has marked this topic as solved on
