How to Install HestiaCP on Ubuntu: The Complete Step-by-Step Guide 2026

Alright, let’s skip the intro speech. If you’re running a VPS on Ubuntu and you’re still managing every domain, mailbox, and database by hand — or you’re tired of paying cPanel prices — HestiaCP is probably what you’re looking for. I’ve installed this panel on more boxes than I can count, from cheap 1GB instances to dedicated servers, and the install process is the same every time. Here’s exactly how it works, and what it gives you.

This guide covers which Ubuntu versions actually work, what’s inside the panel, the step-by-step install, and the post-install tasks I do on every server. Follow it top to bottom and you’ll have a working control panel in about 15 minutes. Let’s get to it.

Here’s the reality most articles won’t tell you: the people who end up on HestiaCP are usually running budget servers where every dollar counts. A cPanel license starts north of $20 per month, which for a small hosting setup can be the entire infrastructure budget. The manual route — hand-editing Nginx configs, mail configs, and MySQL — works, sure, but it eats your evenings and it falls apart at 3 AM when something quietly breaks.

And the “free” panels have their own catch. A lot of them are bloated, barely maintained, or they quietly stop working after a distro upgrade. HestiaCP got its reputation the boring way: it’s stable, it’s actively maintained by a real community, and it runs comfortably in about 1GB of RAM. If that’s the kind of box you’re on right now, you’re in exactly the right place.

Think of it like moving into a new apartment. Day one looks chaotic — boxes everywhere, you can’t find anything. But once the furniture is in, everything has a place, and you stop digging through five tools and three config files just to create a single website. That’s what switching to a control panel feels like. The move takes fifteen minutes; the payoff is every day after that.

What You Actually Get With HestiaCP

Forget the marketing fluff. Here’s what I actually use this panel for, on a daily basis, across real client servers:

• Web Server: Nginx in front, Apache behind it. Fast static delivery, but .htaccess still works. Want it lighter? There’s an Nginx-only mode.
• Multi-PHP: PHP 5.6 up to 8.4, and you pick the version per domain. A legacy app on 7.4 sitting next to a fresh Laravel app on 8.3? No problem at all.
• Database: MariaDB with phpMyAdmin. PostgreSQL is available too if you need it.
• DNS: Bind9 with DNSSEC. Create and manage zones from the web UI — no more editing zone files by hand.
• Mail: Exim for SMTP, Dovecot for IMAP/POP3, Roundcube for webmail. SpamAssassin and ClamAV are optional add-ons.
• FTP: vsftpd, with per-user disk quotas.
• Security: Firewall and Fail2ban are on by default. Let’s Encrypt SSL is literally one click.
• Backups: Local, FTP, SFTP, Amazon S3, Google Drive, Backblaze. Scheduled, rotated, done.
• CLI & API: Every panel function also exists as a v-* command and a REST endpoint. Automation is a first-class citizen here.
• Web Terminal: A built-in browser terminal in recent versions. Genuinely handy when you’re not at your desk.

Which Ubuntu Versions Does HestiaCP Support?

“All versions” needs a quick reality check. HestiaCP supports Ubuntu LTS releases that are still inside their support window. Once a release goes EOL, they drop it — and honestly, that’s a feature, not a bug. The panel needs active repos. Here’s the picture right now:

Still sitting on 20.04 or older? Upgrade to 22.04 or 24.04 before you start. It’s a hassle, but it beats installing a panel on an operating system that’s already past its support date. For the always-current list, the official docs at hestiacp.com are the source of truth.

Before You Start — A 5-Minute Checklist

Almost every install failure I’ve ever seen traces back to skipped prep. Five items, five minutes, no shortcuts:

• A fresh Ubuntu 22.04 or 24.04 instance (x86_64 preferred; recent versions support ARM too).
• At least 1GB RAM, 1 CPU core, 10GB disk. 2GB RAM is the comfortable spot.
• Full root access — either root login or a user with sudo privileges.
• A static IP and a proper FQDN hostname, like server.example.com.
• An A record pointing at your server if you plan to use Let’s Encrypt right away.

Step-by-Step: How to Install HestiaCP on Ubuntu

Step 1 — Log In and Update the System

Get into the server and update everything first. Never start a panel install on a half-updated system — it’s the single most common failure I see.

ssh root@YOUR_SERVER_IP
apt update && apt upgrade -y

If the upgrade pulled in a new kernel, reboot before continuing. Thirty seconds now saves you fifteen minutes of confusion later.

Step 2 — Set an FQDN Hostname

HestiaCP needs a fully qualified hostname. A bare hostname like “ubuntu” will make the installer complain. Set it first:

hostnamectl set-hostname server.example.com

And add it to /etc/hosts so it resolves locally:

echo "YOUR_SERVER_IP server.example.com server" >> /etc/hosts

Step 3 — Run the Installer

This is the part that surprises people. It’s one command:

curl -sS https://hestiacp.com/install.sh | bash

Prefer full control? The script accepts flags for admin email, password, and the exact components you want. Swap the values in quotes for your own:

bash <(curl -sS https://hestiacp.com/install.sh) -e admin@example.com -p 'YourStrongPassword' -y no -f -d server.example.com --nginx --apache --php --mysql --exim --dovecot --named --vsftpd --iptables --fail2ban --multiphp --dnssec

Give it 10 to 15 minutes on a typical VPS. The terminal will go quiet for stretches — that’s it compiling packages, not hanging. Don’t kill the session, and don’t close the SSH connection.

Step 4 — Grab Your Credentials

When it finishes, you get a summary like this. Copy it somewhere safe:

===========================================================
Hestia Control Panel installed
-----------------------------------------------------------
Admin URL: https://YOUR_SERVER_IP:8083
Admin username: admin
Admin password: [randomly generated]
-----------------------------------------------------------

Using the non-interactive command from Step 3? Then the password you passed with -p is the one in effect.

Step 5 — Log Into the Panel

Open https://YOUR_SERVER_IP:8083 in your browser and sign in. From here you can create users, domains, mailboxes, and databases without ever touching a config file again.

Post-Install Tasks I Do on Every Server

Change the Panel Port

Port 8083 is being scanned by bots right now, this very second. Move the panel to a non-standard port from Settings > Panel. It’s a tiny change that cuts brute-force noise dramatically.

Fix the Panel SSL

Self-signed certs mean permanent browser warnings. Enable Let’s Encrypt for the panel:

v-update-letsencrypt

Schedule Backups Now

Not tomorrow. Now. Weekly backups to an external destination — never just the same disk. Our backup strategy guide covers what should go where.

Create Your First User and Domain

Users menu for the account, Web menu for the domain, then drop your files into /home/USER/web/DOMAIN/public_html and create a database from the DB menu. When you’re ready to squeeze more performance out of the web stack, the Nginx optimization guide covers the heavy lifting.

Troubleshooting — Common Install Failures

Here’s the short version of every install problem I’ve run into, and the fix for each:

One more thing before you call it done: lock the box down. SSH keys, a hardened firewall, fail2ban rules — the whole checklist is in our Ubuntu VPS hardening guide. Install a panel, then secure the panel. In that order.

That’s the whole process. Install it, change the port, schedule backups, create your first site. If you hit an error, read the actual log line before you start Googling — nine times out of ten, the log tells you exactly what’s wrong. Now go build something.