Install aaPanel

Install the aaPanel control panel on a WebGee cloud server, and the security steps its default configuration leaves to you.

Install aaPanel, a free control panel with a graphical interface for managing web servers. Applies to VPS and dedicated servers.

This is an unmanaged installation. WebGee supports the server and the network; aaPanel, its updates and its security are yours. See What server management includes.

Before you begin

A clean server — see Rebuild your server.
A currently supported OS: AlmaLinux 8 or 9, Rocky Linux 8 or 9, Debian 11 or 12, or Ubuntu 20.04, 22.04 or 24.04.
Root access — see Connect over SSH.
A domain pointed at the server's IP, if you will serve sites.

Do not follow older guides recommending CentOS 7 or Ubuntu 16.04/18.04. Those releases are end of life and no longer receive security updates.

Install

As root:

# Debian / Ubuntu
wget -O install.sh https://www.aapanel.com/script/install-ubuntu_6.0_en.sh && bash install.sh aapanel

# AlmaLinux / Rocky
yum install -y wget && wget -O install.sh https://www.aapanel.com/script/install_6.0_en.sh && bash install.sh aapanel

The installer prints the panel URL, username and password at the end. Save them — they are not shown again.

First steps

Sign in at the URL shown, typically http://your-server-ip:7800.
Change the password immediately.
Install the software stack you need — the panel offers LNMP or LAMP on first login.
Add your first site under Website → Add site.

Secure it before going live

aaPanel's defaults favour convenience over safety, so these matter:

Change the default panel port from 7800. It is scanned constantly.
Change the admin path from the default in Panel Settings.
Restrict access by IP where you can.
Enable two-factor authentication.
Keep the panel and its stack updated — nobody else will.

The panel is served over plain HTTP by default. Configure a certificate for it before signing in from anywhere you do not control, or your admin password travels in the clear.

If installation fails

Not a clean server. Conflicting web or database packages are the usual cause.
Unsupported OS version.
Not enough memory. Allow at least 1 GB, more with a full stack.