On 3/31/2026 at 2:07 AM, drohack said:

Hey everyone! I built an Unraid plugin that brings Uptime Kuma monitor statuses directly onto the Unraid dashboard as a native widget.

What it does:

- Displays heartbeat bars matching Uptime Kuma's style (green/red/orange/blue) with hover tooltips showing date/time and status

- Uptime percentage badges with color coding

- Configurable time periods (1h, 12h, 24h, 7d, 30d, 90d, 180d)

- Quick link to open Uptime Kuma's WebUI (auto-detected from your Docker container)

- Choose which monitors to display via checkboxes in settings

- Native Unraid dashboard tile with standard controls (settings cog, collapse, etc.)

How it works:

It reads Uptime Kuma's SQLite database directly in read-only mode from the Docker volume mount. No API keys, no background services, no modifications to Uptime Kuma. Supports both v1.x and v2.x (auto-detected).

Install:

Plugins tab > Install Plugin > paste this URL:

https://raw.githubusercontent.com/drohack/UptimeKumaPlugin/main/uptime-kuma.plg

Then go to the plugin settings, set your database path (usually /mnt/user/appdata/uptimekuma/kuma.db), click Test Connection, enable the widget, and check your dashboard.

GitHub: https://github.com/drohack/UptimeKumaPlugin

Feedback and suggestions welcome!

Can you added it to CA for all?

I just installed the docker via unRAID app store and I'm getting this notification that it's outdated. According to unRAID, the docker was updated yesterday

1 hour ago, Marc_G2 said:

I just installed the docker via unRAID app store and I'm getting this notification that it's outdated. According to unRAID, the docker was updated yesterday

I'm pretty sure this is coming from Uptime Kuma itself and not my plugin.
I think you're on Uptime Kuma 1.23.x, because latest is still v1. Uptime Kuma checks GitHub for newer releases, and 2.5.5 is actually out.

Also the plugin works on v1 and v2 and automatically switches it's backend on which one is installed, so it can work with both.

You can switch the container to louislam/uptime-kuma:2 (back up appdata first if you have existing data), or hide the notice under Settings -> About

On 9/28/2026 at 7:29 AM, drohack said:

I think you're on Uptime Kuma 1.23.x, because latest is still v1. Uptime Kuma checks GitHub for newer releases, and 2.5.5 is actually out.

Is this intentional @Cornelius? is 2.x unstable or something?

Otherwise maybe an oversight that latest still points to 1? @CorneliousJD thoughts?

Also if you do update, there's a non-obvious migration step that can take minutes to hours (depending on how long you've been using it; it has to replay full history for its DB upgrade). Log file shows what's happening, but the web page just says Cannot GET /settings/about

Edited 13 hours ago13 hr by froggles
migration details

The template installs upstream's deprecated v1 (latest). Could it move to :2?

Hi @CorneliousJD , thanks for maintaining this template. Following up on @froggles question (page 99): we run this container ourselves, so I checked what latest actually contains.

• Upstream has deprecated latest. The Docker Tags page says: "latest tag is deprecated, which is always pointing to v1. Please consider using Recommended Tags." (wiki). The security policy lists 1 and latest as deprecated and 2 as supported (SECURITY.md).

• The template has no tag, just louislam/uptime-kuma (template), so every install from CA gets v1.

• What latest contains (image built 2026-09-16, checked 2026-10-24): Uptime Kuma 1.23.17 on Debian 10, EOL 2024-06-30 (endoflife.date), with Node.js 18.20.3, EOL 2025-04-30 (endoflife.date), and OpenSSL 1.1. Because the image keeps getting rebuilt, Unraid shows it as freshly updated (Marc_G2), while the app inside stays on 1.23.

• What :2 contains (image built 2026-10-23): Uptime Kuma 2.5.7 on Debian 12, Node.js 22.23.4 and OpenSSL 3. The 2.0.0 stable release came out on 2025-10-20 (release), so v2 is not a beta. The current release is 2.5.7 (releases).

• The template maps the Docker socket for the Docker container monitor, so this container effectively has root on the host. That is one more reason to keep it on supported software.

Anyone can check their own container with: docker exec UptimeKuma sh -c 'grep PRETTY /etc/os-release; node -v; grep -m1 version /app/package.json'

Suggestion: change the template's Repository to louislam/uptime-kuma:2 for new installs, and add a short note to the Overview and the first post with the migration steps below. Upstream calls v1 to v2 "a major version update" with "some breaking changes" (migration guide), so existing users should switch knowingly rather than by surprise.

For anyone switching now (steps from the migration guide):

1. Stop the container and back up /mnt/user/appdata/uptimekuma.

2. Edit the container and set Repository to louislam/uptime-kuma:2. Don't use the rootless tags: upstream says they are "not recommended for upgrading from v1 to v2" (wiki).

3. Apply, then follow the log with docker logs -f UptimeKuma. The first start converts the heartbeat history. Upstream's own 20 monitors with 90 days of data took about 7 minutes, and "On slower hardware or with more monitors, this can take hours." Don't interrupt it: "If the migration process is interrupted, you must restore from backup and retry the upgrade." (migration guide). Until it finishes, the web page only shows Cannot GET (froggles).

4. Check the breaking changes before relying on them: badge durations, SMTP templates (now LiquidJS, case-sensitive), and JSON backup/restore, which has been removed (migration guide).

Thanks again for the template!