Getting started
Requirements
Operating system
| System | Versions | Architecture |
|---|---|---|
| AlmaLinux | 9 (every 9.x release) and 10 (every 10.x release) | x86_64 |
| Rocky Linux | 9 and 10 | x86_64 |
| RHEL | 9 and 10 | x86_64 |
Keep the server on the latest minor release (dnf update); NexPanel installs packages from the current repositories.
Differences on version 10
- Valkey instead of Redis. AlmaLinux 10 ships Valkey, a Redis-compatible store on the same port. NexPanel uses it for the panel's cache and for the mail filter; nothing changes for you.
- Mail lookup tables use LMDB. Postfix on version 10 has no Berkeley DB; NexPanel writes LMDB maps there.
- The default AlmaLinux 10 images need a CPU with x86-64-v3 (AVX2, roughly 2015 or newer). For older CPUs use AlmaLinux's x86-64-v2 build.
Ubuntu and Debian are not supported yet. Install on a fresh, minimal server: NexPanel installs and manages the web server, PHP, MariaDB and mail itself.
Hardware
These are starting points; size up for the number of sites you host.
| Role | CPU | Memory | Disk |
|---|---|---|---|
| All-in-one (testing, a few sites) | 2 vCPU | 4 GB | 40 GB |
| Hosting node | 2+ vCPU | 4+ GB | Enough for your customers' sites, mail and backups staging |
| Controller only | 1–2 vCPU | 2 GB | 20 GB |
Before you install
- Root access to the server (the installer must run as root).
- cgroup v2 — the default on AlmaLinux 9 and 10. The LVE manager needs it.
- No other control panel on the server (cPanel, Plesk, DirectAdmin, CloudLinux LVE).
- OpenSSL 3 — included in AlmaLinux 9 and 10; used to check release signatures.
- For a controller with its own domain: a DNS record pointing the domain at the server, so a Let's Encrypt certificate can be issued.
- Ports:
80and443for websites;2083,2087and2096for the panels in all-in-one mode;25,465,587,993,995if you host email.
LiteSpeed Enterprise
NexPanel can run LiteSpeed Enterprise, but it needs your own LiteSpeed license. When the license expires LiteSpeed stops serving sites; NexPanel shows a Web server down incident on the node overview. You can switch the node to Nginx, Apache, Nginx + Apache or OpenLiteSpeed at any time — see Web servers.
Wrong or missing something? Let us know.