Application logs
Every application has a Logs page that shows the latest lines of its logs. Which logs it offers depends on the application’s type. This page lists them and says how to use the viewer.
Open the logs
Section titled “Open the logs”- Open Applications and choose the application.
- Go to Logs in its menu, under the Logs group.
- Choose a log from the tabs at the top.
The page opens on the application’s own output when it has one, and on the web server’s error log otherwise.
Which logs each type has
Section titled “Which logs each type has”| Log | What it shows | Which applications |
|---|---|---|
| App output (Application log on Joomla) | What the app itself printed: its latest lines, with your environment values hidden. | Node.js, OpenClaw, Hermes Agent and Joomla. |
| Laravel log | The newest file in storage/logs: exceptions and messages your code logged. |
Laravel |
| Queue worker | What the queue worker printed: jobs it ran, retried and failed. | Laravel |
| PHP errors | Errors and warnings from the application’s PHP. | Every type that runs PHP: WordPress, Custom PHP, Laravel, Drupal and Joomla. |
| Nginx errors | Problems the web server hit, such as timeouts and missing files. | Every type |
| Access log | Every request served for the application, oldest first. | Every type |
| Cron jobs | What your scheduled tasks printed when they ran, newest last. | Every type that has scheduled tasks |
Drupal keeps its own log inside its database, so it has no app log here. Static applications don’t run PHP and have no PHP log. WordPress also has a separate debug log under its own WordPress group. See Logs and analytics.
On OpenClaw and Hermes Agent, the agent’s output can contain conversations and personal data. Only the account owner and super admins can read it. Collaborators don’t see it.
Use the viewer
Section titled “Use the viewer”Each log shows its latest lines and refreshes about every 30 seconds while the window is in front. The server’s own logs show their latest 512 KB. For the app output, Laravel and queue worker logs, you see the latest lines the agent could read.
- Click All, Errors or Warnings to filter by level. Each shows how many lines it holds.
- Type in Filter lines to search.
- Use the buttons at the top right to refresh, Copy the log, Download it as a
.txtfile and switch Wrap long lines. - Click the trash button to clear a web server, PHP or cron log. Clearing removes the entries so far, and new ones keep being recorded. The app output, Laravel and queue worker logs are read-only.
The logs of the web server are also in the logs folder of the file manager.
Find out why an app does not start
Section titled “Find out why an app does not start”When a Node.js or AI agent application does not start or keeps stopping, open its App output log first. The messages the process printed while starting, including error messages, are the quickest clue. For a Laravel application, start with the Laravel log, and for a failing job check the Queue worker. For a PHP application, look at PHP errors and Nginx errors.
The same output appears on the app’s own page, under Recent log, for example Node.js › App.
Passwords stay out
Section titled “Passwords stay out”The logs can repeat things your application was given. Netkeel hides the values of your environment variables and common secret patterns, such as keys and passwords, before the text reaches your browser. It cannot recognise everything, so don’t print secrets in your own logs.
Let an AI assistant read them
Section titled “Let an AI assistant read them”An assistant connected through AI assistants (MCP) can read the same logs with the get_application_logs tool, up to 200 lines at a time.