Skip to content

Logs ​

Logs brings every log on the server into one page with a tab per source.

Overview ​

URL: /admin/logs

Logs with the Executions tab open

The tabs, in the order they appear:

TabWhat it shows
ExecutionsEvery action the panel carried out on the server, with its outcome.
Activity LogWho did what in the panel. See Activity Log below.
Apache AccessWeb server access log.
Apache ErrorWeb server error log.
Postfix / DovecotMail delivery and mailbox access.
RoundcubeWebmail.
RspamdSpam filtering.
Fail2BanBans and the rules that triggered them.
VsftpdFTP.
Panel ErrorErrors raised by AdminBolt itself.
Linux SecurityThe system security log.
AgentsBolt Agent activity.

Each tab keeps its own address, so a tab can be bookmarked or linked to directly:

/admin/logs?tab=apache-error

Tabs for optional components, such as LiteSpeed and OpenLiteSpeed, appear once the module is installed.

Executions ​

The Executions tab is the one to reach for when an action in the panel did not do what you expected. Each row carries:

  • Time the action ran.
  • Action that was requested, for example issuing an SSL certificate.
  • Type, which names the target, for example the domain the action applied to.
  • Details, including a correlation ID.
  • Status: success, failed, or completed.

Since panel 1.9.1, clicking a row opens the details of that execution: its source, status, start and completion times, who ran it, the IP address it came from, the error when it failed, and the full output.

Correlation IDs ​

Every run gets a correlation ID, and the same ID appears on the notification the run produced. When a notification tells you something failed, search that ID here to find the run behind it, along with the domain it applied to. This is the link between "something went wrong" and "here is what happened".

Failure notifications state the action, a concrete reason, and the next step. A notification marked as a warning means the operation did succeed, with a caveat worth reading.

Reading the other tabs ​

The remaining tabs read the log files on the machine. They share a search box and a filter button, and show the newest entries first.

Since panel 1.9.3:

  • Refresh, above the table, reads the open tab's log again, so new entries appear without reloading the page. The Executions tab has Truncate Logs there instead.
  • The filters narrow the rows on every tab. The Module filter, for example on Apache Error, keeps the entries of the module you pick, and each text filter keeps the entries that contain what you type.

Since panel 1.9.6:

  • Panel Error keeps whole entries. An entry of the Panel Error tab holds every line written for it, not only the first one. The table shows the first line, the search looks through all of them, and clicking a row opens the entry in full, with its time, level, source, and the whole message.
  • A long log says how much of it was read. The tabs read the newest part of a log. When the log is longer, a note above the table says so: "Showing the newest 1000 lines of this log. Only the newest part of the log is read, so the search and the date range do not reach older lines." When a search or a date range asks for more than was read, the note adds from which point in time the log was searched. An empty result on a long log therefore does not read as "nothing happened".
  • Sensitive values are masked. Passwords, secrets, tokens, cookies, session ids, and similar values in an entry are shown as [redacted] on every tab, as the administrator API returns them, and a search does not match the masked value.

For certificate problems specifically, SSL Issuance History is usually faster: it lists issuance attempts per domain with the reason each one failed.

The administrator API ​

Since panel 1.9.4, the administrator REST API reads the tabs of this page:

Method and pathWhat it does
GET /api/admin/logs/sourcesThe tabs of this page on this server, in their order, each with the filters its entries take. A source whose service is not set up here has no tab and is not listed.
GET /api/admin/logs/sources/{source}/entriesThe entries of one tab, newest first, with its filters, as the tab shows them.

Passwords, secrets, tokens, cookies, session ids, and similar values in an entry are returned as [redacted], and a search does not match the masked value. meta.truncated is true when older entries were not read. A log that has nothing in it yet answers with an empty list. When a log cannot be read, the request fails with 502 rather than returning an empty list. The activity log has endpoints of its own; see Activity Log.

Activity Log ​

Activity Log (/admin/activity-logs) answers a different question: who did what in the panel. Since panel 1.9.3 it is the second tab of the Logs bar instead of a separate sidebar entry, but it stays its own page, described on Activity Log. Use Logs for what the server did, and Activity Log for what people did.