david/homelab-dashboard
1
0
Fork 0
Code Issues Pull requests Projects Releases 76 Packages 1 Wiki Activity Actions
Page: Uptime Kuma
Pages
Container Registry Documentation Screenshots Grimmory Home Kavita Lab View Module Setup Navidrome Notifications Plex Proxmox Roadmap Security Hardening Seerr Requests Storage Health UniFi Network Uptime Kuma White Labeling
4 Uptime Kuma
Codex edited this page 2026-05-22 14:12:47 -07:00
Table of Contents

Uptime Kuma

Dashboard Status

This module is live. The dashboard reads a public Uptime Kuma status page and displays monitor nice names, status lights, links, and recent historical status ticks.

Admin Fields

  • Status JSON URL

What To Use

Use the public status page URL or its matching JSON endpoint. If your status page is:

https://uptime.example.com/status/homelab

you can usually enter that URL directly. The dashboard tries compatible public status-page endpoints such as:

/api/status-page/<slug>
/api/status-page/heartbeat/<slug>

How To Find It

  1. Open Uptime Kuma.
  2. Go to Status Pages.
  3. Open the status page you want the dashboard to summarize.
  4. Copy the public status page URL.
  5. Save it as Status JSON URL in the dashboard.

What The Card Shows

  • Nice monitor name.
  • Current status light.
  • Clickable monitor name when Uptime Kuma exposes a URL.
  • Up to 72 recent heartbeat ticks from Uptime Kuma when the status page exposes heartbeat history.
  • Browser-local fallback ticks when the public endpoint only exposes current status.

The dashboard intentionally hides monitor type and raw URL in the main card to keep the view glanceable.

Test From The Docker Host

curl -fsSL 'https://uptime.example.com/api/status-page/homelab'
curl -fsSL 'https://uptime.example.com/api/status-page/heartbeat/homelab'

A successful response is JSON. If you see HTML, a login page, or a reverse-proxy error, the URL is not the endpoint the dashboard needs.

Common Problems

  • 404: the slug is wrong or the status page is not available at that base URL.
  • 403 or login HTML: the status page is private or protected by SSO/basic auth.
  • Missing monitor names: verify the public status-page endpoint returns monitor metadata, not only heartbeat data.
  • ENOTFOUND: the dashboard container cannot resolve the hostname.
  • certificate errors: the HTTPS certificate is not trusted by Node inside the container.

Sources