Installing a control panel on your server: cPanel, Plesk, DirectAdmin or no panel
This guide explains step by step what a control panel gives you and what it costs, how to choose between cPanel/WHM, Plesk, DirectAdmin and running without a panel, and which prerequisites you need to meet for a smooth installation.
What does a control panel give you, and what does it cost?
A control panel lets you manage the web server, PHP versions, databases, email, DNS zones, FTP and SSL certificates from a single interface. For agencies and resellers, the real gain is being able to give each customer a separate account with its own resource limits and login details. AutoSSL or Let's Encrypt integration renews certificates automatically, and the built-in backup tools back up sites and mailboxes per account.
This comes at a price. The panel license is a recurring cost. Because the panel runs web, email, DNS, database and security services at the same time, it uses a significant amount of memory and disk even when idle. The panel also takes over the server's configuration: changes you make by hand may be overwritten by a panel update, and removing the panel later often means reinstalling the operating system.
Which option suits you?
The table below is general guidance. Supported OS versions and minimum hardware requirements change often, so check the current list in each panel's official documentation before you install.
| Option | Best fit | OS family | Resources and license |
|---|---|---|---|
| cPanel/WHM | Agencies or resellers hosting many sites and email accounts; customers used to cPanel | AlmaLinux, CloudLinux and certain Ubuntu LTS releases | The most resource-hungry option; licensed by number of accounts |
| Plesk | The same interface on Linux and Windows; WordPress-heavy and developer-focused work | Ubuntu, Debian, AlmaLinux; also a Windows Server edition | Medium and up; licensed by edition |
| DirectAdmin | Many sites and mailboxes with fewer resources; a simple interface | The RHEL family such as AlmaLinux and CloudLinux, Debian, Ubuntu | Lightweight; requires a license |
| No panel (Nginx, PHP-FPM, Docker) | A single application or a few sites; a team comfortable on the command line | All current distributions | The lightest option; no license, all maintenance is yours |
If you will run a single application or a few sites, managing the server without a panel is often the faster path with less maintenance; the LEMP installation guide and the Docker guide cover that path. If you are torn between Linux and Windows, see choosing a Linux or Windows server.
Before you install: prerequisites
- A clean operating system: Install panels on a freshly installed system with nothing else added. Nginx, Apache, MySQL or a mail server you installed earlier will conflict with the panel's own services; the installer may stop or break the existing services. If necessary, start over with the Reinstall OS tool in the client area; this deletes all data on the server (see the reinstall guide).
- A supported system: AlmaLinux 9 or CloudLinux for cPanel; Ubuntu 24.04 LTS, Debian 12 or AlmaLinux 9 for Plesk; and supported releases of these families for DirectAdmin are good starting points. Avoid interim releases and end-of-life systems.
- A fully qualified hostname: Use the Change Hostname tool in the client area to set the server name to a fully qualified domain name (FQDN) such as
server1.example.com; only lowercase letters, digits, hyphens and dots are allowed. Create an A record in DNS for this name pointing to the server's IP. The hostname should not be the same as the domain of a site you will host on the server (see hostname and DNS settings). - Memory and disk: As a general recommendation, plan for at least 2 GB of RAM, and 4 GB or more for comfortable use. On disk, leave room for sites, mailboxes, the panel's local backups and updates in addition to the operating system and the panel; the official minimums define what can be installed, not what runs comfortably.
- A restore point: Take a snapshot of the clean system with the Snapshots tool. If the installation fails halfway, you are back at the start in a few minutes. Delete the snapshot once the installation succeeds; a disk cannot be grown while a snapshot exists, and you can keep at most 2 snapshots at a time.
Verify the prerequisites with these commands before installing (if dig is missing, install the dnsutils package on Ubuntu and Debian or bind-utils on AlmaLinux):
hostnamectl # Static hostname must be a fully qualified name
hostname -f # e.g. server1.example.com
dig +short A server1.example.com @1.1.1.1 # must return the server's IP address
cat /etc/os-release # distribution and version
free -h && df -h / # memory and free disk space
ss -tulpn # on a clean system only sshd and a few system services listenLicensing: IP binding and add-on products
Panel licenses are usually bound to the server's IP address. Get the license for the correct IP before you install; if the server's IP address changes, the license has to be updated as well. Alongside WHM/cPanel, Plesk and DirectAdmin licenses, Hostimor also offers licenses for add-on products used with the panels:
- CloudLinux: keeps each hosting account within its own CPU, memory and process limits so that one site cannot slow down the whole server.
- Imunify: malware scanning, a web application firewall and brute-force protection, integrated with the panel.
- LiteSpeed: a web server that replaces Apache and uses fewer resources under heavy traffic.
- JetBackup: incremental per-account backups and self-service restores for customers.
- Softaculous: one-click installation and updates for applications such as WordPress.
You can see every option on the licenses page. If you run into a problem activating a license, open a support ticket from the client area.
Installation: cPanel/WHM, Plesk and DirectAdmin
cPanel/WHM
The official cPanel installer builds and configures every service, so it takes a long time, often more than half an hour. Run it inside tmux or screen so the installation does not stop halfway if your SSH connection drops. When it finishes, open WHM in your browser at https://SERVER_IP:2087, log in as root with your password and complete the initial setup wizard.
# Start inside tmux so the installation keeps running if SSH drops
dnf install -y tmux # on Ubuntu: apt-get install -y tmux
tmux new -s cpanel
cd /home && curl -o latest -L https://securedownloads.cpanel.net/latest && sh latest
# If the connection drops, reconnect and return to the session:
# tmux attach -t cpanel
# Follow the installation log in a separate session:
# tail -f /var/log/cpanel-install.logPlesk
Plesk's one-command installation selects the recommended components and prints the management address at the end; the management interface is at https://SERVER_IP:8443. If you want to choose components one by one, use the interactive installation method in the Plesk documentation.
tmux new -s plesk
sh <(curl https://autoinstall.plesk.com/one-click-installer || wget -O - https://autoinstall.plesk.com/one-click-installer)
# After the installation finishes:
plesk version
plesk login # generates a one-time login link for the administratorDirectAdmin
The DirectAdmin installer asks for your license details and may change between versions. Take the current command from the installation guide in the DirectAdmin documentation; the management interface listens on port 2222 by default. For cPanel as well, confirm the latest requirements in the cPanel documentation.
cPanel cannot be uninstalled once it is installed; to return to a system without a panel, you have to reinstall the operating system. Do not remove the open-vm-tools package during or after the installation: client area actions such as a safe shutdown, password resets, network settings and disk growth are carried out through VMware Tools.
After the installation
Open the required ports in the firewall
Open the ports the panel interfaces and services need: 2083 for cPanel users, 2087 for WHM and 2096 for Webmail; 8443 for Plesk; 2222 for DirectAdmin. If you will host email, you need SMTP (25, 465, 587), IMAPS (993) and POP3S (995); if the server will also answer DNS queries you need 53, and if you will use FTP you need 21 plus the passive port range defined in the panel.
# AlmaLinux / CloudLinux + cPanel (firewalld)
firewall-cmd --permanent --add-service=http --add-service=https
firewall-cmd --permanent --add-port=2083/tcp --add-port=2087/tcp --add-port=2096/tcp
firewall-cmd --permanent --add-service=smtp --add-service=smtps --add-service=smtp-submission
firewall-cmd --permanent --add-service=imaps --add-service=pop3s
firewall-cmd --reload && firewall-cmd --list-all# Ubuntu / Debian + Plesk (UFW)
ufw allow 80,443/tcp
ufw allow 8443/tcp
ufw allow 25,465,587,993,995/tcp
ufw status verboseSome panels disable the existing firewall during installation or write their own rules, and tools such as the Imunify360 firewall or CSF manage their own rule sets too. After the installation, check which tool is active and manage the rules from a single tool; running UFW or firewalld alongside the panel's firewall leads to unexpected blocks or ports left open (see the UFW and firewalld guide).
Verify the installation
# cPanel/WHM
/usr/local/cpanel/cpanel -V # installed version
/usr/local/cpanel/cpkeyclt # re-checks the license
ss -ltnp | grep -E ':(2083|2087|2096)\s'
# Plesk
plesk version
ss -ltnp | grep -E ':(8443|8880)\s'Keep the panel updated and plan backups
cPanel and Plesk update themselves automatically by default; do not turn this off, because panel vulnerabilities are scanned for quickly on the internet. Apply operating system updates regularly as well (see automatic security updates). Enable the panel's backup tool, but remember that those backups stay on the same server: to protect yourself against losing the server, send backups to another location (see the server backup strategy).
Password, hostname and email
- Root password: If you change the password with WHM's root password tool or with
passwd, the Reset Root Password tool in the client area can no longer log in to the server with the stored password. Change the password from the client area. - Hostname: If you need to change the server name after the installation, use the panel's own tool; the panel then updates its own configuration as well, such as certificates and mail settings.
- Email delivery: A reverse DNS (PTR) record for the IP address that points to the hostname helps the email you send get accepted. Send this request in a support ticket; whether it can be applied is assessed based on the IP block. For SPF, DKIM and DMARC, see the business email guide.
Frequently asked questions
Can I install a panel later on a server that already runs sites?
It is not recommended. The panel installs the web, database and email services its own way and may overwrite the existing configuration. The right approach is to back up the data, reinstall the system, install the panel on the clean system and bring the sites back with the panel's migration or import tools.
Can I run a panel on a small package?
The installation may complete with the minimum values, but the panel services use a large share of the memory and leave little for the sites. Track usage with the methods in the resource monitoring guide, and do a resource upgrade if needed.
Do the sites go down if the license expires?
The behavior depends on the panel. When the license cannot be validated, the panel interface and management functions may be restricted; do not count on the sites running unaffected for any length of time. Renew before the due date.
Related articles
Thanks for your feedback!