CloudLinux OS Solo supports all the hardware supported by RHEL/CentOS, with few exceptions. Exceptions are usually hardware that requires binary drivers, and that doesn't have any open-source alternatives.
CloudLinux OS Solo does not support ARM-based CPUs (e.g. Graviton)
With RHEL 8 (CloudLinux 8), some devices are no longer supported. You can check the entire list here.
Downloading installation media
You can download the latest ISO and use it to install CloudLinux OS Solo on your server using this link.
There are multiple ISO types available:
CloudLinux-*-boot.iso- this ISO is made specifically for network installation and does not contain any packages inside.
CloudLinux-*-dvd1.iso- this one contains all packages from the network installation repository, so you can set up any possible configuration without network access.
CloudLinux-*-minimal.iso- this one contains only a minimal set of packages to set up a light server without GUI and Development tools.
Once you install a server from the ISO, make sure you register your system and then run the
yum update command to get all recent updates.
Installing in the Graphical User Interface
The graphical installation interface is the preferred method of manually installing CloudLinux OS Solo. It allows you to have full control over all available settings, including disk partitioning and storage configuration.
The graphical mode is used by default when you boot the system from the local media.
The first screen displayed is the language selection page.
First, find your preferred language in the left column and then select locale in the right one. The selected language will be used during installation and also as a default language of the installed system.
After you select your language and locale, click
Continue to confirm your selection and proceed to the Installation Summary.
The Installation summary screen is the main dashboard of your installation parameters. Most of the options which can be configured during the installation can be accessed from here.
The summary screen displays links to other configuration screens, those links can be in several different states, which are graphically indicated:
Grayed-out link means that the installer is currently updating this section. Please wait a little before accessing this section.
A warning symbol next to an icon means that a screen requires your attention before you start the installation.
Links without a warning symbol mean that the screen does not require your attention. You can still change your settings in these screens, but it is not required to start the installation.
The first thing that you should define is where the system will be installed from. There are basically two options:
- ISO file
- On the network
On the network source
Use this option to download packages to be installed from a network location. This is the preferred way as you automatically receive all critical bug fixes that may affect installation.
Most likely your network is not configured by default, so you can see the URL configuration field greyed out, like on the screenshot below. Please refer to the Network Configuration screen first to set up a network connection.
The correct installation URL for CloudLinux OS Solo is
Type in the installation URL in the corresponding field, configure the proxy if needed and press the
ISO file source
This option is primarily used as an alternative when you don't have an internet connection on a target server. It is only available if you downloaded Minimal or DVD ISO which contains some bundled packages in.
ISO file checkbox and press the
Done, you will be redirected to the Installation Summary screen where Installation source and Software Selection links will be greyed and the
Downloading package metadata message wll be shown.
Please hold on while that message disappears and proceed to the Software Selection section.
The Software Selection screen allows you to choose a Base Environment and Add-ons. These options control which software packages will be installed on your system during the installation process.
This screen is only available if Installation Source is properly configured and only after the installer has downloaded package metadata from the source.
It is not possible to select specific packages during a manual installation, you can only select pre-defined environments and add-ons.
To install CloudLinux OS Solo, first, choose the
CloudLinux OS Solo (minimal) environment on the left of the screen.
All other environments are used to install CloudLinux OS Shared, so make sure you choose
CloudLinux OS Solo (minimal).
Only one environment can be chosen, even if more are available.
Then, on the right side of the screen, select one or more add-ons which you want to install by ticking the check boxes next to each add-on.
Doing that, the
Begin installation button becomes blue, so click it.
After this point, the installation process actually starts and changes are being made to your selected disks. It is not possible to go back to the Installation Summary and change any settings configured there; if you need to do so, you must wait for the installation process to finish, reboot your system, log in and change your settings on the installed system.
The bottom of the screen shows a progress bar and a message informing you of the current progress of the installation. When the installation finishes, you can press the Finish installation button to reboot your computer and log in to your newly installed system.
Before you finish the installation and reboot, either remove the media which you used to start the installation, or make sure that your system tries to boot from the hard drive before trying removable media. Otherwise, your computer will start the installer again instead of the installed system.
Reboot your system, login and check EULA which is located in the
Next, activate your installation in order to get updates.
Converting existing servers
Only CentOS 8/AlmaLinux 8 can be converted to the CloudLinux OS Solo 8.
Sometimes it is required to convert already existing servers with
AlmaLinux and make them
CloudLinux OS Solo.
It is easy to convert your existing installation by cldeploy script. The process takes a few minutes and replaces just a handful of RPMs.
Downloading and running conversion script
If you already have an activation key, run the following commands:
yum install wget -y wget https://repo.cloudlinux.com/cloudlinux/sources/cln/cldeploy bash cldeploy -k ACTIVATION_KEY
ACTIVATION_KEY is the one that you got in the previous step.
If you want to get an IP-based license, run the following commands:
yum install wget -y wget https://repo.cloudlinux.com/cloudlinux/sources/cln/cldeploy bash cldeploy -i --to-solo-edition
After the successful conversion, reboot your system by running the following command:
The script automatically detects and supports the following control panels:
- cPanel with Easy Apache 4
Unfortunately, for now, it is not possible to convert servers with:
- Other control panels that use CloudLinux OS Shared integration.
Please subscribe to our blog, check the news and receive updates.
The cldeploy explanation
By its design, CloudLinux OS Solo is very close to the upstream operating system, RHEL (and so, CentOS and AlmaLinux). This makes the conversion process relatively straightforward, requiring just one reboot.
Here's what the cldeploy script does when you run it:
- Backups the original repository settings into the
- Backups RHEL system ID into the
/etc/cl-convert-saved(RHEL systems only).
- Installs CloudLinux repository settings and imports CloudLinux RPM key.
- Replaces redhat/centos-release, redhat-release-notes, redhat-logos with CloudLinux version.
- Re-installs CloudLinux version of rhnlib/rhnplugin.
- Checks for binary kernel modules, finds replacement if needed.
- Detects OVH servers and fixes the mkinitrd issues.
- Detects Linode servers and fixes the grub issues.
- Checks if LES is installed.
- Checks that the
/etc/fstabhas the correct
- Checks for efi.
- Installs CloudLinux Manager for cPanel Solo.
Reboot your system, log in and check EULA which is located in the
ISO installation provisions server with outdated packages. It is highly recommended to run
yum update right after the first boot.
You can always uninstall CloudLinux OS Solo. In this case, the system will be converted back to CentOS or AlmaLinux.
The following actions will be taken:
- CloudLinux repositories & yum plugin will be removed.
- CentOS or AlmaLinux repositories will be set up.
In the end, the script will provide instructions on how to finish the conversion back. That will require removal of the CloudLinux kernel (a manual step), and installing CentOS or AlmaLinux kernel (if needed).
Do not forget to free up a CloudLinux OS Solo license by removing the server from the Servers section of your CLN account After that, if you don't intend to use the license anymore, you can remove it to avoid being billed.
To uninstall CloudLinux OS, run the following command:
wget -O cldeploy https://repo.cloudlinux.com/cloudlinux/sources/cln/cldeploy sh cldeploy -c
Now you have converted back and it is time to install the kernel.
To delete the CloudLinux kernel, run the following command (change the kernel package name to the one you've been using):
rpm -e --nodeps kernel-2.6.32-673.26.1.lve1.4.27.el6.x86_64
To install a new CentOS or AlmaLinux kernel once you deleted the CloudLinux kernel, run the following command:
yum install kernel
If yum says that the latest kernel is already installed, it is OK. Please check your bootloader configuration before rebooting the system.
To remove unused kmods and lve libs, run the following command:
yum remove lve kmod*lve*
Before the reboot, the following command should be executed for restoring Apache and httpd.conf without mod_hostinglimits:
For EasyApache 3:
For EasyApache 4:
/usr/local/bin/ea_install_profile --install /etc/cpanel/ea4/profiles/cpanel/default.json
Some packages from the CloudLinux repo will still remain. They are the same as CentOS or AlmaLinux packages and don't have to be removed. They will be updated in the future from CentOS repositories, as new versions come out.