Install cPanel & WHM on a VPS: Requirements & Steps
Summary
Pixel’s announcement explains how to prepare a VPS for cPanel & WHM, including supported operating systems, licensing considerations, and why cPanel may not suit a single website. It highlights key OS requirements, such as AlmaLinux versions and Ubuntu 24.04, and warns that Rocky Linux and Debian are not supported for new installs.
DEV Community
Installing cPanel & WHM on a VPS: requirements, the install command and what breaks
Most cPanel installs that fail do so before the installer has really started. The command itself is one line; the work is in giving it a server it is willing to run on. This is the checklist we use, written for developers who are comfortable with SSH but have not set up cPanel & WHM from scratch before. Everything about requirements comes from cPanel's own documentation as it stood in November 2026, so check it again if you are reading this much later. First, decide whether you need it at all cPanel on your own VPS makes sense when you are hosting several sites, for yourself or for clients, and you want the WHM side: creating accounts, setting limits, handing each client their own login. It does not make much sense for one website. The arithmetic is simple. You pay for the VPS, and on top of that you pay cPanel for a licence every month, priced by the number of accounts. Even the single-account tier costs more per month than most shared cPanel hosting plans, which already include the licence and someone else patching the server. If you have one WordPress site and no wish to be root, shared cPanel hosting is cheaper and less work. Install cPanel on a VPS when you have outgrown that, not before. Pick a supported operating system cPanel is narrow about distributions. As of November 2026 the documentation lists: OS Versions Notes AlmaLinux OS 8 (cPanel 110+), 9 (114+), 10 (132+) The default choice for most people Ubuntu 24.04 LTS only PowerDNS is the only supported nameserver; AppArmor can stay on CloudLinux 7, 8, 9, 10 10 needs cPanel 134+; 7 cannot take cPanel 112 or later and is not recommended Rocky Linux none for new installs cPanel now says you can no longer install on Rocky Linux Debian is not on the list, and neither is any Ubuntu release other than 24.04. The Rocky Linux change catches people out because older tutorials still recommend it. If you have no reason to prefer otherwise, take AlmaLinux 9 or 10. One quirk: if the server's IP address already has an active CloudLinux licence, the installer converts AlmaLinux to CloudLinux. Add --skip-cloudlinux to the install command to prevent that. Hardware: minimum and what to actually buy From the AlmaLinux and Ubuntu requirement pages: CPU: 64-bit, 1.1 GHz minimum (Ubuntu page recommends 2 GHz). ARM is not supported. RAM: 2 GB minimum, 4 GB recommended. If you plan to run ClamAV, cPanel strongly recommends at least 3 GB. Below the minimum, the installer refuses to continue. Disk: 20 GB minimum, 40 GB recommended, plus at least 5 GB free in /usr/local/cpanel for installs and upgrades. File system: XFS or ext4. On a single partition, at least 1,000,000 inodes, plus 50,000 per cPanel account. Network: a static, public IPv4 address. IPv6-only servers are not supported, DHCP-assigned addresses are not allowed, and cPanel only licenses publicly visible static IPs with working DNS. Behind NAT, you need 1:1 NAT with NAT loopback. In practice, 2 GB is enough to finish the install and not much more. Start at 4 GB and 40 GB if real sites and mail will live on the box. Start from a fresh OS This is the rule people most want to skip, and it is not optional. cPanel's installation guide says to install only on a freshly installed operating system, and warns that services installed before or during the install cause compatibility problems. That means no Apache, Nginx, MySQL, Postfix or Docker stack you set up "just to test". The installer brings its own web, mail, DNS and database services. There is also no uninstaller. cPanel's documentation says removing it means reformatting the server. So if the VPS has history, back up what you need and reinstall the image. Set a proper hostname The hostname must be a fully qualified domain name on a domain you have registered, must not be the same as any domain you will host on the server, can be at most 60 characters, and must resolve to the server's IP. Use a subdomain, not the bare domain. Create the A record (and AAAA if you use IPv6) first, th...

Powered by Readybot.io