Skip to main content
Open Logs on a running instance and choose a source:
  • System: the VM’s system journal.
  • An app install: the Docker Compose logs for that install’s containers.
The content depends on what the operating system or app writes. Some apps write separate files or require extra logging settings; those messages will not necessarily appear in the app log stream.

​
Read and follow

Choose an initial tail of 50, 100, 500 or 1,000 lines. Use Follow to stream new output and Stop to stop following. You can refresh, copy the displayed output and search the lines currently loaded. The browser keeps a bounded buffer: once it exceeds 5,000 lines, it trims back to the newest 2,500. This is a live troubleshooting view, not an archive. Timestamps and log levels depend on the source.

​
Retrieve older logs

Use the host terminal to query retained system logs:
For a marketplace install, replace the placeholder with its install ID:
These commands can only return logs still retained on the VM. Configure log rotation and a separate collection destination if you need longer retention or logs that survive VM deletion.

​
Troubleshoot an app

  • Startup failure: inspect the output around the last start or restart for missing configuration, permission errors or unavailable dependencies.
  • Webhook failure: compare the sender’s delivery response with app logs. Missing log output does not prove that a request never arrived; the app may not log requests. Check the endpoint, DNS, authentication and sender’s retry history.
  • Slow responses: compare logs with CPU, memory and disk information in Metrics.
Before sharing copied logs, remove credentials, tokens and private request data.

​
Next

Terminal

Query system services and app logs directly.

Files

Inspect logs and configuration stored in files.