Uptime Kuma

Monitoring

Uptime Kuma is a self-hosted monitoring tool that tracks the availability of your services and websites.

Uptime Kuma monitors the availability of your services and provides uptime statistics through its status page API.

Widgets & Capabilities

Adding the integration

Create the connection under Management → Integrations. See Managing integrations.

Status page URL and monitors

Use the Uptime Kuma instance root as the integration URL, and enter only the status page slug in the slug field. For a status page at https://kuma.example.com/status/services, use:

Homarr reads /api/status-page/services and /api/status-page/heartbeat/services from that instance. Both must return JSON reachable from the Homarr server without an interactive sign-in. Do not use /status/services or an API endpoint as the integration URL. Preserve any reverse-proxy base path in the instance URL.

Only monitors in the selected status page's public groups are included. If a monitor is missing, check that it belongs to that status page. A successful connection does not mean every monitor in Uptime Kuma is included.

Troubleshoot authorization errors

Test both JSON endpoints from inside the Homarr container or pod. A 200 response from /status/services only checks the HTML page; it does not confirm that the API paths are accessible:

wget -S -O - 'https://kuma.example.com/api/status-page/services'
wget -S -O - 'https://kuma.example.com/api/status-page/heartbeat/services'

An authorization connection error means an HTTP 401 or 403 response. It does not identify whether Uptime Kuma, a reverse proxy, or an access-control service returned it. Check the response and the relevant proxy logs before changing the slug or credentials. An HTML login page or challenge is not a valid JSON API response.

Certificate errors are a separate failure type. Add a trusted certificate only when the connection reports a certificate validation error; an HTTP authorization error alone is not a reason to add one. See Certificates.

Secrets