Public Status Page

Public Status Page

Boltarr can feed a separate, public status page — showing your users what's up — without exposing Boltarr itself (which holds your network map and SSH keys).

Boltarr only ever pushes a sanitized summary — public name, up/down, uptime, ticks — never IPs, ports, or internal detail — one-way, over your LAN, to a small separate status app.

Architecture

Boltarr (internal, LAN)  ──push (Bearer token)──►  Status app (public-facing)  ──►  visitors

The status app is a tiny container in the repo under statuspage/. Run it on a separate host from Boltarr.

Security: keep Boltarr off the box that hosts the public page. When you eventually expose the status app to the internet, block its /push endpoint at your reverse proxy (Boltarr's LAN push bypasses the proxy and keeps working) so nobody can POST fake statuses.

Set it up

1. Deploy the status app (on its own host): copy .env.example → .env, set a STATUS_TOKEN, docker compose up -d. It serves a read-only page on its port (default 12102).

2. Mark things public:

• Services — a service's detail panel → tick Public status page, optionally set a Public name. Only services that are both monitored and public appear.
• Hosts — a host's Edit dialog → tick Show on public status page + a public name.

3. Configure the push in Settings → 🌐 Public status page: Enabled, the status app URL (e.g. http://status-host:12102), and the shared Token (same value as the app's .env). Push now to verify.

Boltarr pushes on any status change plus a ~60s heartbeat.

The page

Up to three sections, each shown only if it has something public:

• Services — your monitored, public services.
• Hosts — public hosts (server, NAS, etc.).
• Networking — public hosts whose device type is router / gateway / switch / unmanaged-switch / firewall / AP.

Each entry shows an up/down dot, 24-hour uptime %, and a last-hour tick bar. A banner reads "All systems operational" or "Some systems are down".

Router/AP/switch showing under "Hosts" instead of "Networking"? Set the host's device type correctly (Edit Host), then push again. See Troubleshooting.