Logs

Where VMStack writes its logs on the panel server and on nodes, the systemd units and journalctl commands to read them, and the panel's log pages.

When something fails, start with the panel's own log pages: they say what happened in plain words and are filtered per server, node or account. Go to the files and the systemd journal on the panel server or the node when the panel itself does not answer, or a page tells you to look there.

Log pages in the panel#

Page What it shows
System › Tasks Every task sent to a node: its type, server, node, status, progress and the node's message when it failed. Each server's Tasks tab shows that server's tasks.
A server's build log The steps the node recorded while it created or reinstalled the server, and its first boot output. Kept after the server is deleted.
A server's System log tab The last lines the server's console printed, read from the node on request (agent 0.44.0 or later). Lines that look like passwords or tokens are hidden.
System › Audit log Who did what, in the panel and through the API, MCP or the SolusVM layer (via). Every write is there, with its before and after where it applies.
System › Placement log The nodes looked at for each new server, and why each was passed over. Read it when a create fails with "no room".
System › Sign-in log Every sign-in, failure, refusal and ban, with the address and browser.
System › Mail log Every mail sent or tried: status, attempts, the mail server's answer, or why it was skipped.
System › API log Every API request: key, route, status, problem code, duration, address and request ID. Never a body. See API keys.
System › Webhooks (Deliveries) Every webhook delivery and each attempt's answer.
System › Health Whether every queue has a worker, the scheduler runs, scheduled jobs are on time, and each node answers. See Workers and queues.

How long each is kept is set under System › Settings › Logs:

Log Default Range (days)
Audit log 365 90 to 3650
Tasks 180 30 to 3650
Build logs 30 7 to 3650
Sign-in log 90 7 to 365
Placement log 90 7 to 365
API log 30 7 to 365
Webhook deliveries 30 7 to 90
Mail log 90 30 to 365
Usage, 5-minute samples 8 8 to 31
Usage, hourly samples 45 45 to 400
Usage, daily samples 400 400 to 3650

Older entries are deleted once a day at 03:10 UTC. Tasks still waiting or running are never deleted.

When an API client reports an error, ask for the request_id of the error body. It is the same in the API log, in the X-Request-Id header and in the Laravel log.

On the panel server#

The installer puts the panel in /opt/vmstack: the running release is /opt/vmstack/current, and its storage and .env are in /opt/vmstack/shared.

File What is in it
/opt/vmstack/shared/storage/logs/laravel-YYYY-MM-DD.log The application log: errors with their request ID, warnings. One file a day, kept 14 days.
/var/log/nginx/vmstack-panel.error.log nginx errors for the panel's site (a PHP-FPM that does not answer, upstream timeouts).
/var/log/nginx/vmstack-panel.access.log nginx access log for the panel's site.
/var/log/vmstack-panel-install.log Everything the installer, repair and tune ran, with its output.
/var/log/vmstack-panel-update.log Everything panel updates ran.

To follow the application log:

tail -f /opt/vmstack/shared/storage/logs/laravel-$(date -u +%F).log

Panel services#

The panel runs as these systemd units:

Unit What it is
vmstack-panel.target Groups the scheduler, the relay and every worker. Restarting it restarts them all.
vmstack-worker@<queue>-<n>.service One queue worker each: default-1, nodes-1 to nodes-4, dns-1, mail-1, webhooks-1 and webhooks-2 by default.
vmstack-scheduler.service The Laravel scheduler (artisan schedule:work).
vmstack-relay.service The console relay that carries server screens to the browser.
php8.x-fpm, nginx, postgresql, redis-server (or valkey-server) The web server, PHP, database and queue store.
vmstack-panel-backup.timer The daily database dump at 02:30.
vmstack-panel-firewall.service The panel server's firewall (nftables), when the installer set one up.
vmstack-panel-autoupdate.timer, vmstack-panel-update.path Automatic and requested panel updates.
vmstack-panel-cfips.timer Weekly refresh of Cloudflare's address ranges, when the panel is behind Cloudflare.

The quickest overview is the panel's own status command, which lists every unit's state, the certificate, PHP-FPM's status and the queue check:

vmstack-panel status

To read a unit's log:

journalctl -u vmstack-scheduler -n 200 --no-pager
journalctl -u 'vmstack-worker@nodes-*' --since "1 hour ago"
journalctl -u vmstack-relay -f
journalctl -u php8.4-fpm --since today

Replace php8.4-fpm with the PHP version on your server (systemctl list-units 'php*-fpm*' shows it).

On a node#

Where What is in it
journalctl -u vmstack-agent The agent's log, one JSON object per line: requests, tasks, polls, errors.
journalctl -u vmstack-agent-rollback Rollbacks of agent updates that did not come up healthy.
/var/lib/vmstack/tasks/<task-id>.log The step log of tasks that keep one (create, reinstall and similar). The panel shows the same as the build log.
<storage path>/vms/<server-id>/serial.log Each server's serial console output (rotated by virtlogd). The default storage path is /var/lib/vmstack/images.
/var/log/libvirt/qemu/vm-<server-id>.log QEMU's own log for a server: start-up errors, crashes.
/var/log/vmstack-storage-setup.log Every command vmstack-agent storage ran, with its output.

Common commands on a node:

systemctl status vmstack-agent
journalctl -u vmstack-agent -n 300 --no-pager
journalctl -u vmstack-agent --since "2026-11-22 10:00" --until "2026-11-22 11:00"
journalctl -u vmstack-agent -o cat | grep '"level":"ERROR"'
vmstack-agent version

To find a task by its ID (from System › Tasks):

journalctl -u vmstack-agent -o cat | grep 'TASK_ID'

TASK_ID is the task's UUID. The agent's configuration is /etc/vmstack/agent.yaml; its state (records, tasks, samples) is under /var/lib/vmstack.

See also Agent commands and, for updates that roll back, Agent updates.