Operations
Troubleshooting
Logs
| What | Where |
|---|---|
| Agent | journalctl -u nexpanel-agent |
| Controller | /opt/nexpanel-controller/storage/logs/laravel.log |
| Controller updates | /var/lib/nexpanel-updater/update.log |
| Agent / LVE updates | /var/log/nexpanel-update-agent.log, /var/log/nexpanel-update-lve.log |
| Site access and error logs | /var/log/nexpanel/domlogs/<domain>.log and .error.log |
| NexShield events | /var/log/nexpanel-shield/events.log |
| ModSecurity | /var/log/nexpanel/modsec/audit.log |
Most of these are also readable in Servers › Nodes › Logs.
A node shows offline
systemctl status nexpanel-agenton the node — is it running?journalctl -u nexpanel-agent -n 50— look forcontrollers unreachableor TLS errors.- Check that the node can reach the controller URL in
/etc/nexpanel/agent.json.
Jobs stay queued
Jobs wait while the agent is offline. A job that waits for more than 5 minutes shows as an incident on the node overview. Read-only status jobs that never get an answer expire after 10 minutes; changes stay queued until the node is back.
Sites do not load after a change
- Check the web server:
nexpanelctl services. - Test its configuration:
nginx -torhttpd -t. - Regenerate every site's configuration:
nexpanelctl rebuild, then reload the web server. - On LiteSpeed Enterprise, check that the license is valid (
journalctl -u lshttpd).
An update failed
The Updates page shows the log. A failed controller update is rolled back automatically; a failed agent update restores the previous agent. Run nexpanel-updater --check and read /var/lib/nexpanel-updater/update.log for details.
Getting help
Use the contact page and include the NexPanel version (Administration › Updates), the node's agent version and the relevant log lines.
Wrong or missing something? Let us know.