Installation

Last updated

Supported platforms

  • Debian 13 (Trixie) — primary, fully tested.
  • Ubuntu 24.04 (Noble) — supported. The installer detects Ubuntu and takes PHP from the ondrej/php PPA instead of packages.sury.org, and Docker from Docker’s Ubuntu repository.
  • Other Debian and Ubuntu releases are not supported. The installer doesn’t check the release number, so check it before you install; on any other Linux distribution it warns and continues.

Requirements

ResourceMinimumRecommended
RAM2 GB4 GB+
Disk20 GB40 GB+ SSD
CPU1 vCPU2 vCPU+
NetworkPublic IPv4, ports 22/25/53/80/443/465/587/993/995 open+ outbound 53/udp+tcp
OSDebian 13 or Ubuntu 24.04, fresh install—

The RAM guidance matches cPanel: 2 GB is the minimum, 4 GB is recommended. The installer builds the panel (SPA + Go binaries) on the box, so on a ≤4 GB host it provisions a swap file and caps the build’s memory (RAM-aware V8 heap + serialized go build) so compiling doesn’t get OOM-killed — on 2 GB the build is slower but completes. Baseline services (MariaDB, CrowdSec) auto-size down on small hosts; on a very tight 2 GB box you can install without the security module to drop CrowdSec’s ~500 MB WAF engine.

If outbound :53/udp is blocked (some labs), set JABALI_DNS_FORWARDER=<a-reachable-resolver> so the recursor forwards over TCP.

Install

curl -fsSL https://get.jabali-panel.com | sudo bash

On a terminal this opens the installer, which asks what to install. See Choosing modules below.

The installer is idempotent, safe to re-run. It writes drop-ins, never overwrites manual edits to host configs outside of the files it owns.

Environment variables

Put these after sudo, which drops the caller’s environment: JABALI_MODULES=dns sudo bash loses the variable.

VariableEffect
JABALI_MODULES=<keys>Comma-separated optional modules to install; skips the profile picker. See Choosing modules.
JABALI_DNS_FORWARDER=<ip>Force pdns-recursor to forward . to this resolver (use when outbound :53/udp is blocked). Installer also rewrites /etc/resolv.conf to point at the same IP and masks systemd-resolved.
JABALI_HOSTNAME=<fqdn>The server’s hostname, same as --hostname <fqdn>; skips the prompt. The installer sets the system hostname to it and uses it for the server’s own DNS zone and the panel’s primary mail domain.
JABALI_ADMIN_EMAIL=<email>The panel admin’s login email; skips that prompt. Without a terminal it defaults to admin@<hostname>.
JABALI_NS1_NAME=<fqdn>, JABALI_NS2_NAME=<fqdn>Nameserver names when the dns module is on. Default ns1.<hostname> and ns2.<hostname>.
JABALI_PHP_VERSIONS="<v> <v>"Space-separated PHP versions to install side by side. Default 8.4. The last one listed becomes the command-line php; keep 8.4 in the list for phpMyAdmin.
JABALI_TIMEZONE=<zone>Set the server timezone, e.g. UTC or Europe/London. Default: leave it as is.
JABALI_DEFAULT_LOCAL_BACKUPS=1Turn on automatic daily local backups for every user. Off by default.
JABALI_SKIP_* (various)Skip individual install steps. Generally avoid, supported only for debugging.

Choosing modules

The core always installs: nginx with PHP-FPM, MariaDB, Redis, the panel, its agent, and Kratos for sign-in. Everything else is a module you choose.

Interactive install. The one-line install opens the installer. Pick a profile, then adjust the module list:

ProfileModules
Minimalnone
Web hostdns, security, quota
Mail serverdns, mail, security
Fullevery module
Customstarts from Web host

Unattended install. Set JABALI_MODULES to a comma list of module keys. The installer then skips its screens and installs that list. The install command builder writes the whole command for you:

curl -fsSL https://get.jabali-panel.com | sudo JABALI_MODULES=dns,mail,security bash

Left unset, JABALI_MODULES gives the Web host profile. Set but empty, it gives Minimal.

KeyInstalls
dnsPowerDNS: authoritative DNS and per-domain records.
mailStalwart mail server and Bulwark webmail. Needs dns, which is added when missing.
securityCrowdSec, malware scanning (Linux Malware Detect, YARA-X), the UFW firewall and AppArmor.
dockerDocker engine and the admin’s 1-click Docker apps.
docker_appsDocker apps for hosting users. Needs docker, which is added when missing. It doesn’t work in an unprivileged container.
python_appsThe runtime for users’ Python apps.
postgresPostgreSQL alongside MariaDB.
quotaPer-user disk quotas.
apiThe REST API and its keys.

To see what a selection installs without changing anything, add --dry-run:

curl -fsSL https://get.jabali-panel.com | sudo JABALI_MODULES=dns,mail,security bash -s -- --dry-run

If docker, docker_apps or postgres fails to install, the installer warns and finishes the rest. That module’s switch in the panel stays off, so you can turn it on there later.

After the install. Turning a module off hides its pages in the panel; existing data is kept (see Module flags). Server Settings → Modules turns dns, mail, security, quota and api on or off. Docker, Docker apps for users and Python apps are under Server Settings → Apps; PostgreSQL is under Server Settings → Databases. From the shell, install.sh --install-module KEY installs dns, mail, security, quota or ftp on an installed server.

What the installer does

  1. Verifies root, a Debian or Ubuntu system, no conflicting cPanel/Plesk/CyberPanel install.
  2. Adds Sury PHP repository (PHP 8.1–8.5+) and PackageCloud for CrowdSec.
  3. Purges sury-nginx if present — Jabali uses Debian-native nginx (Sury dropped nginx in 2026; this is defensive).
  4. Installs system packages: nginx, mariadb, php-fpm (all current Sury versions), redis, certbot, restic, ufw. The modules add their own: pdns-server and pdns-recursor for dns; Stalwart for mail; CrowdSec, Linux Malware Detect (LMD) and YARA-X for security, which also sets up the UFW firewall; Docker for docker; postgresql for postgres.
  5. Installs Kratos, and with mail Bulwark (Node SPA bridge), on Unix sockets — no TCP :4433/:4434/:3000 exposure.
  6. Builds jabali-panel-api (Go) and jabali-agent (Go), writes systemd units, starts services.
  7. Runs DB migrations.
  8. Prints the panel URL, the admin username and a generated password.

Post-install

jabali repair --diagnose   # 7-detector self-heal report
jabali update              # pulls latest code, rebuilds, migrates, reloads

Diagnostics:

journalctl -u jabali-panel.service -f
journalctl -u jabali-agent.service -f
jabali system diagnostic   # redacted, encrypted support bundle

Uninstall

Redeploying the VM is the cleanest teardown. To keep the host, run the installer’s uninstall as root, from a downloaded copy of install.sh:

bash install.sh --uninstall                          # asks before each destructive step
bash install.sh --uninstall --yes                    # no prompts
bash install.sh --uninstall --purge-packages --yes   # also purge the OS packages

Its prompts read the terminal, so don’t pipe it from curl unless you pass --yes. Each step is best-effort: a step that fails is skipped and the uninstall goes on, so it also cleans up after an install that stopped half-way.

It removes, without asking:

  • the jabali-* services and timers with their drop-ins, and the drop-ins Jabali added to nginx, MariaDB, CrowdSec and Redis;
  • the Jabali binaries, and /etc/jabali/, /etc/jabali-panel/ and /etc/stalwart/, including the panel’s own certificates;
  • /var/lib/jabali*, /opt/jabali* and /var/log/jabali*. This includes the local backups in /var/lib/jabali-backups: copy any you want to keep first;
  • the mail store in /var/lib/stalwart, so all mail in every mailbox;
  • Redis and its data. Redis is purged even without --purge-packages;
  • the nginx vhosts Jabali wrote, its PHP-FPM pools and AppArmor profiles, and its CrowdSec, audit, nftables, sysctl, SSH and DNS drop-ins;
  • the system accounts jabali, jabali-mail, jabali-webmail and stalwart, and their groups.

It asks before:

  • dropping the panel’s databases jabali_panel, jabali_pdns, jabali_kratos and stalwart_smtp, with their MariaDB users. --yes drops them.
  • removing users with a home directory under /home: all of them, none, or one by one. The list holds every account with a UID of 1000 or more, not only the ones Jabali created. --yes never removes them; remove any you want with userdel -r <user> afterwards.
  • purging the OS packages Jabali installed. With --purge-packages it purges them without asking. With --yes alone it keeps them.

It leaves:

  • the customers’ own databases, and the MariaDB server unless you purge the packages;
  • /var/www, apart from /var/www/jabali-disabled;
  • /etc/letsencrypt;
  • the users and their /home directories, unless you chose to remove them.

--purge-packages purges nginx, MariaDB, PowerDNS, PHP (every installed version), Node.js, certbot, CrowdSec and its bouncers, auditd, AppArmor, AIDE, UFW, restic and the other tools Jabali installed, then runs apt autoremove --purge. Generic tools such as git, curl and rsync stay. Purging MariaDB can delete every database on the host, the customers’ too: back them up first.

There is no jabali command for this: only install.sh --uninstall.

Known good install paths

  • KVM / QEMU on a clean Debian 13 cloud image, works.
  • LXC unprivileged, not supported (cgroup v2 host requirements + systemd-user timers fail in unprivileged containers).
  • LXD privileged on a recent host, works.
  • Docker / nspawn, not supported as the panel host (the panel itself uses systemd-machined for some operations).