Choosing a VPS control panel: cPanel, Webmin or ISPConfig

Choosing a VPS control panel: cPanel, Webmin or ISPConfig

This picks up from a server you can already reach over SSH. If you need to deploy one first, see our Linux VPS page.

Pick cPanel if you are running commercial shared or reseller hosting and are happy to pay for a licence. Pick Webmin if you want a free, general system administration UI and to keep full control of the operating system. Pick ISPConfig if you want a free hosting panel with admin, reseller and client roles and you are comfortable following Linux stack guides.

Before you start

• How you manage your Hostworld VPS: you control power, rebuilds, VNC and ISO mounting in Virtualizor, which you reach from the Hostworld client area at portal.hostworld.uk. This is separate from any control panel you install inside the VPS.
• You may not need a control panel at all: if you are hosting one site for yourself and you are happy on the command line, a panel adds overhead. If you are hosting for others, want email accounts, or need per-customer isolation, a panel helps.
• Fresh OS requirement: both cPanel and the ISPConfig autoinstaller expect a freshly installed, empty operating system. Installing on a used server often fails or leaves you with an inconsistent stack. cPanel has no uninstaller. The only way back is a full OS reinstall, which destroys data if you have not backed up.
• Licensing and IPs for cPanel: cPanel licences are separate from the server and billed monthly. It licences only publicly visible static IPv4 addresses and requires a resolvable FQDN hostname. NAT or a missing FQDN will block installation and licensing.
• OS support:
  • cPanel: supports AlmaLinux 9 and Ubuntu 24.04 LTS. On AlmaLinux, SELinux must be disabled. On Ubuntu, AppArmor is compatible.
  • Webmin: runs on AlmaLinux and Ubuntu, among others.
  • ISPConfig: supports Ubuntu 24.04 and AlmaLinux 8 to 10. Ubuntu 24.04 support arrived in ISPConfig 3.2.12.
• Resources: cPanel lists 2 GB RAM and 20 GB disk minimum, with 4 GB RAM and 40 GB disk recommended. A full mail and antivirus stack on any panel tends to need about 4 GB RAM or more to run well. Webmin with a “web only” stack can work around 1 GB, but add mail, spam and antivirus and you should plan around 4 GB.
• Ports and firewalls: the ISPConfig installer uses Let’s Encrypt on port 80 and serves its UI on port 8080. Do not block those during install. For cPanel, leaving OS firewalls active during installation can cause key import or SSL failures. If you keep a firewall, ensure the installer can reach package mirrors and required services.
• Commercial focus: cPanel is built for hosting providers. It uses its own tools to manage Apache, PHP and updates. Manual edits to its managed configuration files are unsafe because they are overwritten by rebuilds. Webmin writes your distro’s native configs and expects you to know what you are changing. ISPConfig sits between those, managing standard services while staying close to distro conventions.

At a glance

Step 1: Decide what you are trying to run

Be clear about your workload and who it serves. Your answer drives the choice.

• Reselling shared hosting or running many customer cPanel accounts: pick cPanel. It has the account model, per‑account isolation and workflows your customers expect. Budget for the monthly licence.
• One or a handful of sites for yourself or your organisation, and you like full control: pick Webmin. It is a general admin UI that leaves the system as the system. You can also mix Webmin with the command line.
• Hosting panel without licence costs, with admin/reseller/client roles and multi‑server capability: pick ISPConfig. Be ready to follow its install guide on a clean OS and to manage the underlying services.

Step 2: Check OS, IP and hostname requirements

Run through these before you install anything.

• Operating system: for cPanel use AlmaLinux 9 or Ubuntu 24.04 LTS. For ISPConfig use Ubuntu 24.04 or AlmaLinux 8 to 10. Webmin works on both.
• Fresh install: cPanel and the ISPConfig autoinstaller must start from a clean OS with no preinstalled web or mail stack.
• Networking for cPanel: allocate at least one publicly routable IPv4 address and set a resolvable FQDN hostname. Licencing and installation fail without both.
• SELinux and AppArmor: disable SELinux on AlmaLinux before installing cPanel. AppArmor on Ubuntu is compatible with cPanel.

Step 3: Size your VPS

Under‑sizing a control panel leads to poor performance or failed services. Plan for headroom.

• cPanel minimums: 2 GB RAM and 20 GB disk. cPanel recommends 4 GB RAM and 40 GB disk. If you enable antivirus and spam filtering for mail, expect memory use to grow. cPanel notes 3 GB or more for ClamAV alone. Real‑world full stacks are happier at 4 GB or more.
• Webmin with Virtualmin bundle: around 4 GB RAM for a LAMP/LEMP stack plus mail, spam and antivirus. Minimal web‑only installs usually work around 1 GB RAM.
• ISPConfig: the mail stack is memory‑intensive because amavisd loads SpamAssassin internally. Plan RAM accordingly.

If you need to change plan with us, you can upgrade your VPS resources in the Hostworld client area. If you reach the point where you need help, open a support ticket.

Step 4: Prepare a clean starting point

Preparation avoids the most common failures.

• Rebuild the VPS if needed: in Virtualizor you can rebuild to a clean AlmaLinux 9 or Ubuntu 24.04 image from the Hostworld client area. This is the right move if you have experimented and now want to commit to cPanel or ISPConfig.
• Avoid preinstalling services: do not add Apache, Nginx, MySQL, Postfix or similar before running cPanel or the ISPConfig autoinstaller.
• Mind the firewall: if you keep a firewall during installation, ensure installers can reach package mirrors and that ISPConfig can use ports 80 and 8080. Blocking those breaks Let’s Encrypt and the panel UI.

Step 5: Weigh the trade‑offs on abstraction

• cPanel: you manage Apache, PHP and related components through WHM and EasyApache 4. Manual edits to files like httpd.conf are overwritten by rebuilds. Use cPanel’s include files or interfaces when you need customisation. System updates for cPanel‑managed components should go through cPanel’s update tools rather than raw apt or yum.
• Webmin: it edits your distro’s native configuration files. You can switch between Webmin and the command line. This is flexible and quick for admins who know what they are changing. It is also risky. Webmin runs with root privileges, so mistakes can break services or stop the system booting.
• ISPConfig: it manages standard services such as Apache or Nginx, BIND or PowerDNS, mail and FTP. It supports multi‑server setups. It remains close to distro conventions, which makes it approachable if you know the stack.

Step 6: If you choose cPanel, install on AlmaLinux 9 or Ubuntu 24.04

Read this section in full before you start. cPanel installation is one way. Reversing it requires a reinstall of the operating system.

6.1 Check the core requirements

• AlmaLinux 9 with SELinux disabled, or Ubuntu 24.04 LTS.
• At least one publicly routed IPv4 address and a resolvable FQDN hostname.
• 2 GB RAM and 20 GB disk minimum. 4 GB RAM and 40 GB disk recommended.
• No preinstalled web or mail stack.

6.2 Run the installer

This command downloads the latest cPanel installer to /home, then runs it. It takes a while and reconfigures the system for cPanel.

AlmaLinux 9

cd /home && curl -o latest -L https://securedownloads.cpanel.net/latest && sh latest

Ubuntu 24.04

cd /home && curl -o latest -L https://securedownloads.cpanel.net/latest && sh latest

During initial setup in WHM you will need to provide your licence. A free 15‑day trial is available from cPanel if you want to evaluate first. Remember the licence is billed separately from your VPS plan.

6.3 Update cPanel the supported way

This command runs cPanel’s update script. Use this rather than raw package manager updates for cPanel‑managed components.

/usr/local/cpanel/scripts/upcp

6.4 Configure Apache and PHP the supported way

Use WHM’s EasyApache 4 interface and include files. Editing Apache’s main configuration files directly leads to your changes being overwritten. cPanel documents how to layer custom includes so they persist across rebuilds.

6.5 Common pitfalls to avoid

• Installing on a used server. If you already tried other services, rebuild the VPS in Virtualizor first.
• Forgetting the IPv4 and FQDN hostname requirements. Misconfigured or NAT‑only servers fail to licence.
• Leaving SELinux enabled on AlmaLinux. cPanel requires SELinux disabled.
• Blocking outbound connections or key ports during install. This causes package key imports or SSL issuance to fail.

Step 7: If you choose Webmin, plan how you will operate it

Webmin is free and open source and provides a general‑purpose system administration UI. It edits your distribution’s native configuration files and lets you mix UI changes with command line edits. That flexibility is the appeal and the risk.

• Start from a clean OS if you want a bundle: if you plan to add a hosting stack such as LAMP or LEMP, install on a fresh AlmaLinux 9 or Ubuntu 24.04 base so package dependencies are clean.
• Respect that it runs as root: small mistakes have big consequences. Know what a setting does before changing it.
• Match resources to features: web‑only sites can run with modest RAM. If you add mail, spam and antivirus, plan around 4 GB RAM. That guidance matches the experience reported for the common Virtualmin bundle.

Webmin is a good fit if you are the person operating the VPS and you want to keep the system close to stock. If you want multi‑tenant accounts and customer‑facing self‑service, look to cPanel or ISPConfig instead.

Step 8: If you choose ISPConfig, follow the autoinstaller expectations

ISPConfig is free and open source and provides a full hosting panel with admin, reseller and client roles. It can manage Apache or Nginx, BIND or PowerDNS, mail and FTP, and supports multi‑server setups.

• Use a fresh OS: the official autoinstaller expects a freshly installed, empty base system. Do not layer it on a used server.
• Open ports during install: do not block port 80, which the installer uses for Let’s Encrypt, or port 8080, which serves the ISPConfig UI. Also allow ports for the services you plan to run.
• Mind memory for mail/AV: the “Perfect Server” guidance notes that amavisd loads SpamAssassin internally. Disabling a separate SpamAssassin service is a common memory optimisation. The point is that mail and AV are memory‑intensive. Plan RAM accordingly.
• Pick your stack deliberately: Apache or Nginx, and BIND or PowerDNS, are choices you make up front. Keep to one set unless you have a reason to change.

ISPConfig suits admins who do not want to pay for a licence, need a hosting panel structure, and are comfortable running the underlying services.

Step 9: Be honest about cost and who each one suits

• cPanel cost: licence billed separately from the server. As of the current pricing: Solo (1 account) $29.99 per month, Admin (up to 5) $35.99, Pro (up to 30) $53.99, Premier (100+) $69.99 plus $0.49 per account over 100. There is a free 15‑day trial.
• Webmin and ISPConfig cost: both are free and open source.
• Who they suit: cPanel for commercial shared and reseller hosting. Webmin for administrators who prefer hands‑on OS control. ISPConfig for a no‑cost hosting panel with roles and multi‑server capability.

Step 10: Avoid the common ways this goes wrong

• Installing cPanel on a used server or next to other web or mail services. The installer can fail or leave you stuck. Removal requires reinstalling the OS.
• Forgetting the IPv4 and resolvable FQDN hostname for cPanel. Licencing fails without them. Misconfigured NAT breaks installs.
• Editing Apache or PHP configs directly on a cPanel server. EasyApache 4 rebuilds overwrite those files. Use cPanel’s include files and interfaces.
• Blocking key ports during installation. For ISPConfig, port 80 and port 8080 must be reachable. For cPanel, restrictive firewalls during install can block key imports or SSL issuance.
• Under‑provisioning RAM when enabling mail antivirus and spam filtering. Plan around 4 GB RAM or more for full mail stacks. cPanel notes 3 GB or more for ClamAV alone.

If you need a hand choosing or want us to check your plan against what you intend to host, open a support ticket. Tell us your VPS plan, OS, and what you plan to run.

What next

• If you have chosen cPanel, proceed to installation and first‑time WHM setup on a fresh AlmaLinux 9 or Ubuntu 24.04 VPS. Keep the points above in mind about licensing, SELinux on AlmaLinux, and updates through cPanel’s tools.
• If you have chosen Webmin or ISPConfig, line up a clean OS and follow their official install documentation closely, paying attention to ports and service choices.

If you do not yet have a server, pick a plan on our Linux VPS page. For more articles on operating a VPS with Hostworld, see our VPS guides. If you get stuck, open a support ticket so we can help from your account.