How to install aaPanel and prepare your first website

Installing aaPanel does not automatically finish your application environment. The panel is installed first; you then choose a web server, PHP and a database.

1. Choose a clean system

Use a fresh Linux image supported by the current installer and root access. Confirm it against the official quick start.

Record your application's PHP version, extensions, database engine and storage needs before installing anything. A backup is much easier to restore when you know the runtime it expects. Avoid installing over another panel.

2. Download and install

For an Ubuntu or Debian host:

bashsudo -i
apt update
apt install -y curl ca-certificates
curl -fsSL https://www.aapanel.com/script/install_panel_en.sh -o /root/install_panel_en.sh
bash /root/install_panel_en.sh forum

These commands keep HTTPS verification enabled. If the download fails, investigate DNS, the system clock and CA certificates.

Save the complete administrative URL and credentials printed at the end. Do not guess a fixed port or omit a security path. To display the connection information again:

bashbt default

Treat that output as sensitive. Check free disk space before accepting the installation location.

3. Install a compatible stack

Choose one web server for your application, then install the required PHP and database components. Wait for the installation tasks to finish. Do not run separate Apache and Nginx instances competing for the same listener.

4. Create the website

Add the domain from Website, select its document root and PHP version, and create a dedicated database user if needed. The Website documentation covers the available settings.

Upload into the correct directory. A framework's public directory is not necessarily its project root. Verify that configuration secrets cannot be downloaded over HTTP.

5. Validate DNS and TLS

Point public DNS at the server, including any IPv6 record, and issue a certificate:

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

For 502 responses, inspect the application or PHP process. For 403, inspect the root, index file and ownership. If the wrong site appears, check domain mapping and DNS before changing permissions.

6. Back up the application

Protect the management URL with an IP restriction or VPN. Back up both files and database, then test a restore. Panel settings alone may not recover the application. Continue with the security checklist and database maintenance guide.