Panel and licensing problems

Messages from the VMStack panel installer, panel updates and licensing, what each one means, and how to fix it.

This page lists the messages you are most likely to meet while installing, updating and licensing the panel, with the fix for each. The logs to look at first:

What Where
Install /var/log/vmstack-panel-install.log
Updates /var/log/vmstack-panel-update.log
Workers, scheduler, relay journalctl -u 'vmstack-*'
The panel /opt/vmstack/shared/storage/logs/laravel-<date>.log
nginx /var/log/nginx/vmstack-panel.error.log

vmstack-panel status shows every service and whether each queue has a worker.

Installer refuses the server#

The installer checks the server before it changes anything; when it stops here, nothing has been installed.

Message Fix
"Debian 12 is not supported (it is in LTS since June 2026). Install the panel on Debian 13, Ubuntu 24.04 or Ubuntu 26.04." Reinstall the server with Debian 13.
"… is not supported. Install the panel on Debian 13 (recommended), Ubuntu 24.04 or Ubuntu 26.04." Same.
"systemd is not running as PID 1: the panel needs it (OpenVZ and WSL are not supported)." Use a virtual machine, or an LXC container with systemd.
"This server has … MiB of memory; the panel needs at least 2 GiB" / "… CPU; the panel needs at least 2" Give the server at least 2 vCPU and 2 GiB.
"Only … MiB are free on the file system of /opt; the panel needs 20 GB" Free or add disk space (also on /var/lib/postgresql).
"This server is (or looks like) a VMStack node. …" The panel and a node never share a server. Install the panel on another server. The message lists what it found (the agent, libvirt, QEMU).
"Port(s) 80 443 are in use. …" Stop what listens there (ss -ltnp shows it), or use a fresh server.
"apache2 is installed. …" (or caddy, lighttpd), "nginx already serves other sites" The panel needs a server of its own. apt purge the other web server, or use a fresh server.
"PostgreSQL here already has databases (…). …" The panel uses a PostgreSQL of its own. Use a fresh server.
"No terminal to ask on: run with --yes --domain --email
."
Run from an interactive SSH session, or give the answers as options.
"--licence-key '…' is not a licence key (VMS-STD-XXXX-XXXX-XXXX-XXXX)." Copy the key again from your vmstack.eu account.

Domain check fails#

Message Fix
"panel.example.com has no A or AAAA record. …" Add the record, wait until getent ahosts panel.example.com shows it on the server, run the installer again.
"panel.example.com points to 198.51.100.7, not to this server (203.0.113.10). …" Correct the record, wait for it to resolve, run again. Behind NAT, where the public address is not on the server, add --skip-dns-check.
"panel.example.com is proxied by Cloudflare. Set it to DNS only for the install, or run with --behind-cloudflare." See Cloudflare.

The certificate is self-signed#

The install finished, but the summary says Certificate: self-signed in red with Let's Encrypt's reason. The API and the console do not work in browsers until a trusted certificate is in place.

  1. Fix the cause. Usually: the domain does not resolve to the server yet, port 80 is blocked by a firewall in front of the server, or Let's Encrypt's rate limit for the domain was reached (wait, or test with --staging-cert).
  2. Run vmstack-panel cert.

The install stopped halfway#

Run the installer again with the same command. It continues from the step it stopped at, with the answers it saved. If a step fails again, its message and the install log say why. A failed health check names the part that failed (for example a queue no worker took); vmstack-panel status and journalctl -u 'vmstack-*' show more.

vmstack-panel admin-link [email protected]

When it answers that the administrator "has set its password already", use Forgot password on the sign-in page (mail must be set up), or have another administrator reset it.

Update check fails#

System › Settings › Updates shows the last check's error.

Message Fix
"No queue worker picked up the check; is the default worker running?" Run vmstack-panel status; start the workers with systemctl restart vmstack-panel.target.
"The update address answered … with something that is not a release file", or an HTTP error "from Cloudflare" A proxy or a firewall in front of the panel's internet access answers instead of the release server. Allow outgoing HTTPS from the panel.
A manifest "refused as a replay" An older release manifest was served than one already seen (a stale cache or mirror). Nothing to do: the next check of the real feed works.

Update now does not start#

The page says "The updater has not started in 2 minutes." The panel asks for an update by writing a request file, and a systemd path unit starts the updater as root.

systemctl status vmstack-panel-update.path
systemctl enable --now vmstack-panel-update.path

Or run the update directly: vmstack-panel update. Take the request back on the page cancels the request.

The update was not installed#

Result Meaning and fix
Postponed: "Queue jobs still running after 15 minutes: …" Long jobs (such as a mass mail) were running. Nothing changed. Automatic updates try again in the next window; or click Update now again later.
"Release … needs PHP …; this server runs PHP …" The release needs another PHP version, which the updater does not install. Install the PHP version and its extensions the message names, then run vmstack-panel update.
"Release … cannot run here: …" The new release's checks failed (a PHP extension, the database, the cache, disk space, or a node's agent older than the release needs). Fix what it names; for old agents, see Agent updates.
"pg_dump failed: the database was not backed up, so nothing was changed." Usually a full disk. Free space in /opt/vmstack/shared/backups.
"Another update is running" Wait for it; /var/log/vmstack-panel-update.log shows it.

The update was rolled back#

The panel runs the previous version again, and the version that failed is marked failed: automatic updates skip it until a newer release. The Updates page and the update e-mail give the reason (for example "The health check failed for 120s: …" or "The migrations of … failed"). The log is /var/log/vmstack-panel-update.log.

  • Send the reason to VMStack support; a fixed release follows.
  • Update now tries the failed version again if you want to.
  • The database dump taken before the update is in /opt/vmstack/shared/backups/pre-<version>.sql.gz. The updater never restores it; when migrations ran, the status shows the commands to restore it by hand. You rarely need them, because the previous release runs on the newer database.

Update now stays disabled with "Needs a panel installed by the VMStack installer." on panels that were not installed by the installer.

Trial problems#

Message Fix
"Free email providers are not accepted. Please use a business or company email address." Use an address at your company's domain.
"The domain of this address cannot receive email. Please check the address." The domain has no mail (MX) record. Use an address that receives mail.
"This panel already had an evaluation licence. …" One trial per panel install. Buy a licence, or contact VMStack.
"An evaluation licence was already issued for example.com. …" One trial per organisation domain. Use the key of that trial on this panel if it is still running, or buy a licence.
"An evaluation for this panel is waiting for verification at another address. …" Use the link sent to that address, or wait until it expires (24 hours).
"The confirmation link expired. Send a new one." Send the link again and confirm within 24 hours.
The licence page keeps saying it waits for the link Open the link and click Confirm and issue my licence (opening the link alone does not confirm). Keep the licence page open; it checks every 10 seconds.

Activation problems#

Message Fix
"This is not a valid licence key. Check it for typos: VMS-STD-XXXX-XXXX-XXXX-XXXX." A character is wrong or two are swapped. Copy the key from your vmstack.eu account.
"This licence is in use on another panel. Remove it there, or move it to this panel in your vmstack.eu account." Remove it on the old panel, or use Move to a new install in your account. See Activate a licence.
"This licence was moved too often lately. …" 3 moves in 30 days is the limit. Contact VMStack support.
"vmstack.eu could not be reached: …" The panel needs outgoing HTTPS to vmstack.eu. Check the server's firewall, DNS and proxy.
"vmstack.eu sent a licence token this panel does not trust: …" The panel is too old to know the key the token is signed with, or something between the panel and vmstack.eu changed the answer. Update the panel, then try again.
"The install secret cannot be read (was APP_KEY changed?). Remove the licence and activate it again." APP_KEY in .env is not the one the licence was activated with. Put the original APP_KEY back (from a backup); otherwise Remove licence, then activate the key again.

New servers are blocked#

The banner and the licence page give the reason:

Reason Fix
"This panel has no licence yet. …" Start a trial or activate a key in System › Settings › Licence.
"This panel's licence expired on … (it could not be refreshed from vmstack.eu, or the licence ended)." Check Last refresh failed: on the licence page. Restore the panel's outgoing HTTPS to vmstack.eu, or renew the licence in your account; then Refresh now.
"vmstack.eu no longer licenses this panel: …" The licence was moved, suspended, revoked or has ended. Check it in your vmstack.eu account, then activate a valid key.
"This panel has … nodes; its licence covers …. New servers are blocked since …" Delete a node you no longer use, or raise the allowance in your account; then Refresh now.
"Node … already has 10 servers, the most this panel's licence allows on one node." The node is a Small node and full. Choose another node, make it an Unlimited node, or buy more Unlimited nodes. See Small and Unlimited nodes.

Customers and resellers only see "New servers cannot be created at the moment. Please contact support."

A node refuses new servers for the licence#

The panel is licensed, but a creation on one node fails because the node refused it. The node's Agent panel, row Licence, shows what the node thinks of the licence and why.

  • "The node refused the new server: it has no valid licence from this panel." The panel sends its licence with every call to the node, so the node should receive it at the next poll. Check that the panel's licence is valid, and that the node is online.
  • A node keeps the panel install that first licensed it, and refuses a licence for another install. This happens when the panel was reinstalled instead of restored from its panel backup. Enrol the node again: Enroll again on its page, then run the new install command on the node with --force.
  • "The node refused the new server: it already holds the most servers this panel's licence allows on one node." See the Small limit above.
  • A node with an agent older than 0.60.0 refuses the token of a licence with both Unlimited and Small nodes. Update its agent (Agent updates).
  • "Not reported (agent before 0.58.0)": the agent is too old to report its licence state. Update it.

A node that refuses to enrol for the licence stays pending; the panel keeps trying and sends its licence each time, and the pending node's page says why.