Installer stopped with an error (and how to fix it)

For server administrators · Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes and fixes
  3. Still not working?
  4. Common questions

The installer checks the server before it changes anything. When a check fails it prints ERROR: with the reason and stops. Fix the cause and run the same command again.

Symptoms

The installer ends with a red ERROR: line. The full output is in /var/log/sahaab-install.log.

Causes and fixes

"Run as root"

Log in as root, or start the command with sudo.

"Ubuntu 22.04 or 24.04 required"

The server runs another system or version. Reinstall the server with Ubuntu 24.04 (recommended) or 22.04 from your hosting provider's control page.

"Unsupported architecture"

Only 64-bit x86_64 and aarch64 servers are supported.

"At least 2 GB of RAM is required" / "At least 20 GB of free disk space is required"

Choose a larger server plan, or free space on /.

"Another control panel is installed"

The server already has a hosting control panel. Installing over it would take over its web server, DNS and mail. Use a separate, fresh server and move the accounts with the Transfer Tool.

"Apache is running. Use a fresh server."

Use a fresh server. Many provider images with a "LAMP" stack include Apache; pick a plain Ubuntu image.

"Port … is already in use. Use a fresh server."

Something already listens on port 80, 443, 25, 2083 or 2087. See what it is:

ss -tlnp | grep -E ':(80|443|25|2083|2087) '

Use a fresh server, or remove that program if you are sure the server is not in use.

"The license agreement was not accepted. Nothing was installed."

Run again and type yes at Do you accept the license agreement?. Unattended installs need --accept-license.

"Unattended install: [email protected] is required."

Add --email= with a valid address (and --hostname= with a full name).

"Ubuntu's updates have held the package system for 30 minutes."

A new server installs its own updates in the first minutes and the installer waits for them. If it waited 30 minutes, check with ps aux | grep apt, let the update finish or reboot, then run the installer again.

Still not working?

Read the last lines of the log:

tail -n 50 /var/log/sahaab-install.log

Unless error reports are turned off, the failing step is reported to the panel's maker automatically, with addresses and names removed, so it can be fixed.

Common questions

Is it safe to run the installer again?

Yes. When the panel is already installed, the installer keeps its configuration and data.

The installer warned about the hostname but continued.

That is a warning, not an error. Add the A record later; the panel's certificate is issued once it points to the server.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.