Appearance
Troubleshooting
Most problems show up in one of three places: Server → Services, Server → Logs, or the aio command on the server.
aio doctor
As root:
bash
aio doctorIt checks the things the panel depends on: the operating system is supported, the PHP repository matches the release, Nginx and the mail services are running, the panel can read its database, certificates are in place, and Fail2ban's SSH jail is active. On Debian it also checks that nft and rsyslog are installed. Each line is OK, a warning, or a failure, with a short hint.
A website shows the wrong page or a 502
- Open the website and read the error log (the button on the site, or Server → Logs).
- If it is a PHP site, check Server → PHP for that version and Account settings for the owner. A pool that is stopped returns 502.
- If it is a Node.js or Python app, open Node.js & Python, look at the app's status and the last lines of its log, then restart it.
- Server → Services → Nginx → Restart. If Nginx will not start, the last configuration change was rolled back; the service log says why.
Mail is not arriving or not leaving
- Email → Queue & Delivery shows the queue and the last log lines. A message stuck with "connection timed out" usually means the provider blocks port 25. Turn on the outgoing relay.
- Email → Domains runs the deliverability check (MX, SPF, DKIM, DMARC, PTR). Use Fix for the records the panel can write itself.
- If sending worked and then stopped after an update,
aio doctorand a Postfix restart (Server → Services) are the first checks. The panel re-applies the relay when it starts.
I cannot sign in
- Too many failures locks the address for the lockout window (Settings → Security). Wait, or remove the row from the server:
aio setting:setis documented in Installation. - If you set an IP allowlist and locked yourself out, SSH to the server and run
aio setting:set security.ip_allowlist [], then restart the panel withaio restart. - The panel listens on port 8282 unless you changed it.
aio statusprints the URL.
The panel itself will not start
bash
aio status
aio logsA failed update rolls back on its own. If it did not, aio logs shows the Node.js error. The usual cause on an old server is a Node.js older than 22.12; aio doctor reports the version.