Common control panel installation errors

Quick answer: Nine out of ten failed panel installs come down to five causes: a non-fresh OS (existing web/DB packages), an unsupported OS version, too little RAM, a hostname that is not a valid FQDN, or the panel port blocked by a firewall. Start from a clean OS that matches the panel's requirements and the installers "just work".

Overview

Panel installers configure whole software stacks, so they are strict about their starting conditions. This article is a checklist for diagnosing a failed or half-finished installation of CloudPanel, CyberPanel, aaPanel, HestiaCP or cPanel on a Cloud2Y server.

Before you start

• The installer's on-screen error or its log file (installers print the log path when they fail).
• Your server specs and OS version: cat /etc/os-release, free -h, df -h.

Step-by-step guide

1. Check the OS is fresh: ss -tlnp showing anything on :80/:443/:3306 means leftovers — reinstall the OS rather than uninstalling by hand.
2. Check OS support: CloudPanel = Debian/Ubuntu; HestiaCP = Debian/Ubuntu; cPanel/CWP = AlmaLinux/Rocky; CyberPanel/aaPanel = both families. Also match the version (e.g. Ubuntu 22.04/24.04, not 20.04 for new installs).
3. Check resources: 2 GB+ RAM and 10–20 GB free disk; add swap on tight servers.
4. Check the hostname: hostname -f should return an FQDN (cPanel and mail-capable panels require it):

   hostnamectl set-hostname srv1.example.com

5. Check network/firewall: the installer needs outbound HTTPS; you need the panel port inbound (8443 CloudPanel, 8090 CyberPanel, 8888 aaPanel, 8083 HestiaCP, 2087 WHM) — see UFW guide.
6. Fix the finding, reinstall the OS if the failed run left partial packages, and rerun the installer.

Common issues

• "Port already in use": another web server is running — fresh OS required.
• Installer killed at random points: OOM on low-RAM servers — watch dmesg for kill messages, add RAM/swap.
• curl/wget TLS errors: system clock wrong — fix time sync, then retry.
• Panel installed but unreachable: it's listening (check ss -tlnp) — the firewall or your office network blocks the port.

When to contact support

We are happy to reinstall the OS fresh or check server-side networking — open a ticket. Debugging a third-party panel's internals on an unmanaged server is outside the support scope, but we will make sure the platform under it is healthy.

Frequently asked questions

Why does the installer say a port is already in use?

Another web or database server is already running, meaning the OS is not fresh. Reinstall the operating system from the Client Area and run the panel installer on a clean image.

The panel installed but I cannot open it — why?

If "ss -tlnp" shows the panel listening, the block is a firewall: open the panel's port (8443, 8090, 8888, 8083 or 2087) in UFW/firewalld, and check your office network too.

Can support finish a failed panel install for me?

Panels are third-party software on an unmanaged server, so their internals are outside the support scope — but we will gladly reinstall the OS fresh and verify the platform is healthy.

Related articles

• Which control panel should I choose?
• How to install CloudPanel
• How to install cPanel
• Control panel security checklist

Need a hand? Contact Cloud2Y support →