Install CloudPanel with a verified installer and a PHP site

Use a clean Ubuntu 24.04 LTS server for this example. Start with a simple PHP site so you can separate infrastructure problems from application migration problems.

1. Prepare resources and access

The requirements list a baseline of one core, 2 GB RAM and 10 GB disk. Allow additional capacity for databases, uploads and backups.

Reserve a panel hostname and restrict 8443 at the provider firewall to your administrative IP. Keep SSH accessible.

2. Prepare packages

bashsudo -i
apt update
apt upgrade -y
apt install -y curl wget sudo ca-certificates

Complete any necessary reboot. Do not install over an existing control panel.

3. Verify before executing

Open the Ubuntu 24.04 tab in the official installation instructions. This example selects MariaDB 10.11; check application compatibility.

Copy the current SHA-256 checksum from that page. The following block asks for it and runs the script only if verification succeeds:

bashcurl -fsSL https://installer.cloudpanel.io/ce/v2/install.sh -o /root/cloudpanel-install.sh
read -r -p "Official SHA-256: " CLOUDPANEL_SHA256
printf '%s  %s\n' "$CLOUDPANEL_SHA256" /root/cloudpanel-install.sh | sha256sum -c - && DB_ENGINE=MARIADB_10.11 bash /root/cloudpanel-install.sh

A mismatch needs investigation. Check whether the upstream installer changed; do not remove verification to continue.

4. Create the account and site

Immediately create your administrator at https://SERVER_IP:8443. Use Add Site to create a PHP website, choose its user and runtime, and copy files into the displayed document root. The site documentation explains application choices.

Use dedicated database credentials. Store secrets outside publicly downloadable content. Configure application SMTP separately; do not assume website installation migrates email.

5. Test before moving traffic

After DNS resolves correctly, request the site certificate and inspect:

bashcurl -I https://site.example.com

For 502, check the application or PHP service. For 404, compare the document root with file locations. For database failures, test the configured account rather than substituting root credentials.

Check panel login, application login and uploads separately. Restore a file/database backup into a test environment before moving live traffic. Continue with website migration and SSL setup.