> This instance's stack lists every container your compose file starts, Homerun itself, Postgres and Traefik included, with its state. Click one to open its live log. Traefik's is…
> Source: https://orochibraru.com/homerun/docs/system-logs · Site index: https://orochibraru.com/llms.txt

# System Logs

`/system-logs` (admin-only) live-streams the logs of the infrastructure Homerun
depends on, with the same push-based viewer the per-service
[logs panel](https://orochibraru.com/homerun/docs/observability#logs) uses.

**This instance's stack** lists every container your compose file starts,
Homerun itself, Postgres and Traefik included, with its state. Click one to open
its live log. Traefik's is where routing problems show up: a service that
deployed fine but returns 404, a certificate that won't issue, a middleware that
isn't attaching. The list only appears when Homerun runs as a Docker Compose
service; run from source, the app's own output is whatever your terminal or
process manager is already capturing.

App-level warnings and errors that mention a specific service are also persisted
and surfaced on that service's [Observability tab](https://orochibraru.com/homerun/docs/observability#errors).

Opening Traefik also shows two buttons above its log, both behind a confirmation
dialog:

- **Restart**, restarts the Traefik container in place. Useful after a change
  Traefik only reads at startup (its static config/flags).
- **Update**, pulls the image reference Traefik is already running
  (`traefik:v3`, or whatever tag your compose file pins) and, if that pull
  produced a genuinely newer image, recreates the container from it with the
  same configuration, restarting it if it was running. If the pull returns the
  image already in use, nothing is recreated and it tells you so. Pinning an
  exact version tag means this is a no-op by design, which is the point of
  pinning.

Neither button edits your compose file. A `docker compose up -d` later still
brings Traefik back with whatever that file says.