Install Hestia Control Panel (the VestaCP Fork) on Debian 13 or Ubuntu 26.04
VestaCP's stable installer targets CentOS 5-7, Debian 7-9 and old Ubuntu releases. Install Hestia Control Panel, its maintained fork, on Debian 13 or Ubuntu 26.04 instead.
This guide gives a fresh Debian 13 or Ubuntu 26.04 LTS server a web hosting control panel with the Vesta look and command set: web, DNS, mail, databases, FTP, firewall and Let's Encrypt certificates managed from one interface on port 8083. It uses Hestia Control Panel, the actively maintained fork of VestaCP, because the stable VestaCP installer cannot be used on any operating system that still receives security updates.
VestaCP today, and why this guide uses Hestia
VestaCP's own install page lists RHEL/CentOS 5, 6 and 7, Debian 7, 8 and 9 and Ubuntu 12.04 to 18.10 as supported systems, and states that the current version of Vesta is deprecated while a 2.0 release is announced. Every one of those systems is end of life: CentOS 6 since November 2020, CentOS 7 since June 2024. The project's GitHub repository says development resumed in February 2024 and carries new per-distribution installer scripts, but its README labels them beta, in-progress work. That is not something to put a production mail and web server on.
Hestia Control Panel is based on the VestaCP code, is released under the GPL v3 and is updated regularly; its 1.10 series supports Debian 12 and 13 and Ubuntu 22.04, 24.04 and 26.04 LTS on x86_64 and ARM64. It does not support the RHEL family, so if you came here for CentOS, AlmaLinux or Rocky Linux, the answer is to deploy Debian or Ubuntu for the panel server. The v-* command-line tools, the port and the general layout will be familiar to anyone who has used Vesta.
Requirements
- A fresh installation of Debian 13 (or 12) or Ubuntu 26.04 LTS (or 24.04 / 22.04), 64-bit. Hestia must be installed on a clean system; do not install a web server, database or mail server first.
- At least 1 GB of RAM if you leave out ClamAV and SpamAssassin; 4 GB is recommended with the full mail stack. 10 GB of disk is the minimum.
- Root access over SSH. The installer refuses to run as another user.
- A fully qualified hostname for the server, for example
panel.example.com, with a DNS A record pointing to the server's IP address (203.0.113.10in the examples).
Prepare the server
Log in as root and bring the system up to date:
apt update && apt -y full-upgradeMake sure wget and the CA certificates are present, so the installer can be downloaded over HTTPS:
apt -y install wget ca-certificatesDownload and run the installer
Download the installation script from the project's release branch:
wget https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.shRun it with the default component set. The script shows what it is going to install, asks for confirmation, and then prompts for the admin e-mail address and the hostname:
bash hst-install.shBy default you get Nginx in front of Apache, PHP-FPM, BIND, MariaDB, Exim, Dovecot, ClamAV, SpamAssassin, vsftpd, an iptables firewall and Fail2Ban. Installation takes roughly ten to fifteen minutes. When it finishes, the script prints the panel URL, the admin user name and the password; the same details are mailed to the address you entered. Reboot when the installer suggests it.
Choosing components
Every component can be switched on or off with an option. List them all with:
bash hst-install.sh -hFor example, a small server with Nginx and PHP-FPM only (no Apache), no antivirus or spam filter, and all answers given up front:
bash hst-install.sh \
--hostname panel.example.com \
--email admin@example.com \
--username paneladmin \
--password 'use-a-long-random-password' \
--apache no --clamav no --spamassassin no \
--interactive noOther useful options are --multiphp with a comma-separated list of PHP versions, --postgresql yes, --named no if DNS is hosted elsewhere, and --port to move the panel away from 8083. The project also publishes an install-string generator in its getting started documentation.
Log in to the panel
Open the panel in a browser:
https://panel.example.com:8083Until a proper certificate is installed, the browser warns about the self-signed certificate; accept it once and log in with the admin credentials shown by the installer. Create a separate, regular user for the websites you host and keep the admin account for server administration.
Secure the panel with Let's Encrypt
With the hostname resolving to the server, request a certificate for the panel and the mail services from the root shell:
v-change-sys-hostname panel.example.com
v-add-letsencrypt-hostThe first command is only needed if the hostname was not set correctly during installation. If validation fails, the log is in /var/log/hestia/; a proxied DNS record or an AAAA record that does not reach the server are the usual causes.
Add a user and a website from the command line
Everything the web interface does is also available as a v- command in /usr/local/hestia/bin. To create a user, add a domain to it and issue a certificate for the domain:
v-add-user deploy 'another-long-password' deploy@example.com
v-add-web-domain deploy example.com
v-add-letsencrypt-domain deploy example.com www.example.comThe site's files go in /home/deploy/web/example.com/public_html.
Firewall and updates
Hestia manages iptables itself. Add or change rules in the panel under the server settings, Firewall, or with v-add-firewall-rule; rules added to iptables by hand are flushed whenever Hestia updates the firewall. Do not run UFW or firewalld next to it. To move the panel to another port:
v-change-sys-port 2083Hestia is installed from its own APT repository, so the panel is updated together with the rest of the system:
apt update && apt upgradeRelease notes and upgrade instructions between operating system versions are in the Hestia documentation.
Frequently asked questions
Can I still install the original VestaCP?
The script at vestacp.com still exists, but the project itself calls that version deprecated and it only targets end-of-life distributions. The new installers in the GitHub repository are marked beta. For a server that hosts real sites and mail, use a maintained panel.
Does Hestia run on AlmaLinux, Rocky Linux or CentOS Stream?
No. Hestia supports Debian and Ubuntu LTS only, on x86_64 and ARM64. Non-LTS Ubuntu releases and 32-bit systems are not supported either.
Can I install Hestia on a server that already runs websites?
No. The installer expects a clean operating system and configures the web, mail, DNS and database services itself. Install it on a new server and move the sites over afterwards.
How much memory does the full stack need?
ClamAV is the heavy part. On a 1 GB server install with --clamav no --spamassassin no; with 4 GB you can run the complete mail filtering stack comfortably.