The panel runs on a server of its own: a small virtual machine is enough. The installer checks every point on this page before it changes anything, and stops with a message saying what is wrong and how to fix it.
Operating system#
| Supported | |
|---|---|
| Systems | Debian 13 (recommended), Ubuntu 24.04 LTS, Ubuntu 26.04 LTS |
| Architectures | x86_64 (amd64) and arm64 |
| Init system | systemd must be running as PID 1 |
| Virtualisation | A virtual machine or dedicated server. An LXC container with systemd works. |
Not supported:
- Debian 12. The panel installer refuses it. (Nodes still accept Debian 12; see Nodes.)
- Older Ubuntu releases and the RHEL family (AlmaLinux, Rocky Linux and others).
- OpenVZ containers and WSL.
Size#
| Minimum | Recommended | |
|---|---|---|
| CPU | 2 vCPU | 4 vCPU |
| Memory | 2 GiB | 4 GiB |
| Free disk | 20 GB on the file system of /opt, and 20 GB on the file system of /var/lib/postgresql |
40 GB |
The installer refuses a server with fewer than 2 vCPU or less than about 1.8 GiB of memory as the kernel reports it. Below the recommended size it still installs, and the summary says the server is "fine to try, tight for production".
The installer tunes PHP-FPM, PostgreSQL, Redis and nginx for the CPU and memory it finds. After you resize the server, run vmstack-panel tune (see Repair and uninstall).
A fresh server#
The panel installs its own nginx, PostgreSQL and Redis, so the server must not already be in use. The installer refuses a server that has:
- something listening on port 80 or 443;
- Apache, Caddy or lighttpd installed, or nginx serving a site other than the distribution's default;
- a PostgreSQL cluster holding databases other than the default ones;
- anything of a VMStack node: the agent,
/etc/vmstack/agent.yaml,/var/lib/vmstack, libvirt or QEMU packages, or a runninglibvirtd.
The last rule exists because the panel holds the certificate authority that every node trusts, while a node runs your customers' code. Keeping them on separate servers keeps a guest escape away from that authority. /dev/kvm on its own is not a reason to refuse: many cloud servers have it.
Domain name#
The panel needs a host name, such as panel.example.com, with A and/or AAAA records pointing at the server before you run the installer. The installer compares the records with the server's own addresses:
- No record: refused.
- A record pointing somewhere else: refused, with the addresses it found and the server's own.
- Cloudflare's addresses (the record is proxied): refused unless you pass
--behind-cloudflare. See Cloudflare. - Behind NAT, where the record points at a public address the server does not have: pass
--skip-dns-check.
The installer gets a Let's Encrypt certificate for the domain over HTTP, so port 80 must be reachable from the internet during the install and at every renewal.
Ports#
| Direction | Port | What for |
|---|---|---|
| In | TCP 80 | Let's Encrypt challenges; everything else is redirected to HTTPS |
| In | TCP 443 | The panel, the API, the console (WebSocket at /relay/), agent downloads for nodes |
| In | TCP 22, or the ports sshd uses |
SSH. The installer reads the configured ports and keeps them open. |
| Out | TCP 8443 to every node | The panel calls each node's agent (mutual TLS). The port can differ per node. |
| Out | TCP 443 | Release downloads, Let's Encrypt, vmstack.eu licensing, mail providers' APIs, DNS providers, webhook receivers |
| Out | Your SMTP port | Mail, once you set it up |
Nodes never open connections to the panel except to download the agent and its updates over HTTPS. The installer turns on a firewall that lets in only SSH, 80, 443, ICMP and replies. When ufw or firewalld is already active, it adds its rules there instead. --no-firewall leaves the firewall alone.
Time#
The panel's certificates for nodes and two-factor codes need an accurate clock. When no NTP service is running, the installer turns on systemd-timesyncd.
What to back up#
Everything the panel needs to come back on another server is its database and /opt/vmstack/shared/.env. The certificate authority is stored in the database, encrypted with the APP_KEY from .env, so neither works without the other. See Panel backup and restore.