Logs
Read an application's access and error logs in the panel — filter them, follow them live, and clear them.
Logs reads the two log files the web server writes for this application.
No SSH, no tail -f.
The two tabs
Access log is every request that reached the application. Error log is what the web server and the runtime complained about. They are separate files and separate tabs.
The header tells you how much you are looking at — "173 lines — the whole file" — and, importantly, that "Times are the server clock", not your browser's.
Narrowing it down
| Control | What it does |
|---|---|
| Filter lines… | Plain substring match against the lines on screen. |
| All / Errors / Warnings+ | Filters by severity. In the access log, by status class. |
| Last 200 lines | How much of the tail to load. Raise it to look further back. |
| Sort | Flips between newest-first and oldest-first. |
| Copy | Copies what is on screen, so you can paste it into an issue. |
| Refresh | Re-reads the file now. |
Live follows the file as it is written — useful when you are reproducing a request and want to watch it land.
Clear log truncates the file. It is destructive and the panel colours it accordingly.
Reading an access log
Status codes are coloured, which makes the shape of a problem visible before
you read a single line. A page of 404s for /.env, /.git/config,
/config.json and similar is not a bug in your application — it is the
background noise of the internet, and it is the reason the
Web Firewall and
Fail2ban screens exist.
Logs are per application
These are this application's files, not the server's. For system-wide logs — the panel's own, the web server's main log, authentication — use Server → System Logs.