Services and health checks
Manual services make UniHomelabDash useful before any privileged integration is enabled.
Service fields
Section titled “Service fields”| Field | Purpose |
|---|---|
| Name | Clear card and navigation label |
| URL | Address opened by the Open action |
| Icon | Short icon, emoji, or visual identifier |
| Category | Groups related applications |
| Host | Records the device or system serving it |
| Notes | Non-sensitive operator context |
| Health-check URL | Address fetched by the server when you run a check |
Edit or delete services from the Services page overflow menu. The dashboard is optimized for quick status and opening applications. Open always opens the service in a new tab; tapping elsewhere on a card does nothing, so scrolling on a phone never launches an app by accident.
Health states
Section titled “Health states”- Healthy — the configured URL returned HTTP 2xx or 3xx.
- Degraded — the request completed with another status or a useful error.
- Unknown — no check has run yet, or no health URL is configured.
The last-checked timestamp helps distinguish a current result from old state. Use Check all when you want a fresh snapshot. Check buttons show progress while a check runs. On the Services page, a card without a health URL links straight to its edit form.
Attention-first behavior
Section titled “Attention-first behavior”Degraded services appear once, in a Needs attention section above the rest (listed under Other services), so a phone-sized dashboard answers the most important question first. This is a status view, not a monitoring system: checks do not run in the background and there are no alert notifications yet.
Safe health URLs
Section titled “Safe health URLs”Only add addresses you trust the UniHomelabDash server to request. Health checks are server-side and there is no SSRF allowlist in the current release. Never put credentials in a health URL.