Install CloudLinux on a cPanel Server (cldeploy)

CloudLinux OS adds per-account resource limits (LVE), file system isolation (CageFS) and multiple PHP versions to a cPanel server. On an existing AlmaLinux or Rocky Linux server you do not reinstall: the cldeploy script converts the running system in place.

MdmHost shared, reseller and master reseller plans already include this, fully managed. This guide is for administrators running their own cPanel VPS or dedicated server with root access.

Before you start

A cPanel server on AlmaLinux 8/9 or Rocky Linux 8/9 with root SSH access.
A CloudLinux licence: an activation key, or an IP-based licence registered to the server's IP.
A full backup or provider snapshot. The conversion changes the kernel and needs a reboot.
Console access (VNC/IPMI) from your provider in case the server does not come back after rebooting.

Convert the server

Connect over SSH as root and update the system:
```
dnf -y update
```

Download the conversion script:

wget https://repo.cloudlinux.com/cloudlinux/sources/cln/cldeploy

Run it with your activation key:
```
sh cldeploy -k YOUR_ACTIVATION_KEY
```
For an IP-based licence use sh cldeploy -i instead.
Wait for the script to finish; it swaps repositories, installs the CloudLinux kernel and LVE packages and detects cPanel.
Reboot:
```
reboot
```

Check the conversion

uname -r; lvectl list | head

The kernel name should contain el8/el9 with CloudLinux branding (on CloudLinux 8+ the standard kernel includes LVE support), and lvectl should list LVEs.

Enable CageFS

Install and initialise it:
```
dnf -y install cagefs; cagefsctl --init
```
Enable it for all users (recommended), or one by one, in WHM → Plugins → CloudLinux Manager → CageFS.

What CageFS does for users is explained in CageFS explained.

Open CloudLinux Manager and set defaults

Go to WHM → Plugins → CloudLinux Manager (installed with the lvemanager package; run dnf -y install lvemanager if it is missing).
Open Users or Packages and set default limits: SPEED (CPU), PMEM, IO, IOPS, EP and NPROC.
In Options, decide whether resellers get their own limits interface and whether users see Resource Usage.
In Selectors, enable PHP, Node.js and Python selectors as needed (see PHP Selector for users).

Tip: Start with generous limits and tighten them after a week of data in Historical Usage. Limits that are too tight cause 508 errors for customers (see the 508 troubleshooting guide).

Troubleshooting

cldeploy says the licence is invalid

Check the key, or that the IP licence matches the server's public IP. Outbound access to cln.cloudlinux.com must be allowed.

Server does not boot after conversion

Use your provider's console to boot the previous kernel from the boot menu, then contact CloudLinux support with the cldeploy log in /var/log/cldeploy.log.

Customers get 508 errors after enabling limits

Raise EP and NPROC in CloudLinux Manager and see fixing 508 errors.

Frequently asked questions

Does converting delete cPanel accounts?

No. Accounts, files and settings stay in place; only the operating system packages and kernel change.

Can I go back to AlmaLinux?

CloudLinux provides an uninstall procedure, but it is rarely clean. Treat the conversion as permanent and keep a backup.

Was this guide helpful?

Still stuck?

Ask MdmHost AI for a quick answer, or open a ticket and our team will take a look. We are here 24/7.

Ask MdmHost AI Open a ticket