Uptime Kuma
Self-hosted monitoring tool that checks uptime of HTTP, TCP, ping, DNS and other services and sends notifications.
Tested on LinuxKnown vulnerabilities
Use it
Before you install: known vulnerabilities
pickfit found 48 known high or critical vulnerabilities (58 findings, one per affected package version) in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.
npm:mysql2 2.3.3MySQL2 for Node Arbitrary Code Injection (GHSA-4rch-2fh8-94vw, critical, fixed in 3.9.7)npm:protobufjs 7.2.6protobufjs has an arbitrary code execution issue (GHSA-xq3m-2v4x-88gg, critical, fixed in 7.5.5)
See 8 more
npm:mysql2 2.3.3— GHSA-fpw7-j2hg-69v5 (critical), fixed in 3.9.4npm:tar 6.1.15— GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19npm:@grpc/grpc-js 1.7.3— GHSA-5375-pq7m-f5r2 (high), fixed in 1.9.16npm:@grpc/grpc-js 1.7.3— GHSA-99f4-grh7-6pcq (high), fixed in 1.9.16npm:@grpc/grpc-js 1.7.3— GHSA-m9gg-hp2v-232j (high), fixed in 1.13.6npm:axios 0.27.2— GHSA-3g43-6gmg-66jw (high), fixed in 0.31.1npm:axios 0.21.4— GHSA-3g43-6gmg-66jw (high), fixed in 0.31.1npm:axios 0.27.2— GHSA-43fc-jf86-j433 (high), fixed in 0.30.3
48 more findings not listed here.
Linux x86_64
You need first
- Runtimes:
node>=20.4 - System packages:
git
These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:
mkdir -p "$HOME/work" && cd "$HOME/work"git clone the repo
git clone https://github.com/louislam/uptime-kuma.git && cd uptime-kumanpm run setup (checks out 2.5.11, npm ci --omit dev, downloads prebuilt dist)
cd uptime-kuma && npm run setup
Verified in pickfit: the commands exactly as its sandbox ran them
For the record only: they name the sandbox's home, /home/sbx.
git clone https://github.com/louislam/uptime-kuma.git && cd uptime-kumacd uptime-kuma && npm run setupcurl -sS -X POST -H 'Content-Type: application/json' -d '{"dbConfig":{"type":"sqlite"}}' http://127.0.0.1:3001/setup-database && sleep 15 && curl -sS http://127.0.0.1:3001/api/entry-pagecd /home/sbx/work/uptime-kuma && node server/server.js --data-dir=/tmp/kuma-datacurl -sS -X POST -H 'Content-Type: application/json' -d '{"dbConfig":{"type":"sqlite"}}' http://127.0.0.1:3001/setup-database && sleep 15 && curl -sS http://127.0.0.1:3001/api/entry-pageCheck that it works
curl -sS -X POST -H 'Content-Type: application/json' -d '{"dbConfig":{"type":"sqlite"}}' http://127.0.0.1:3001/setup-database && sleep 15 && curl -sS http://127.0.0.1:3001/api/entry-pageThe output should contain “{"ok":true}”.
First thing to try
cd "$HOME"/work/uptime-kuma && node server/server.js --data-dir=/tmp/kuma-datacurl -sS -X POST -H 'Content-Type: application/json' -d '{"dbConfig":{"type":"sqlite"}}' http://127.0.0.1:3001/setup-database && sleep 15 && curl -sS http://127.0.0.1:3001/api/entry-pageOpen http://127.0.0.1:3001 in a web browser; the first screen asks you to set up the database and create an admin account.
What it does
- Monitor uptime of HTTP, TCP, ping, DNS and DockerNot tested
- Send notifications to more than 90 servicesNot tested
- Host multiple status pagesNot tested
- Show certificate informationNot tested
How far pickfit got
Linux x86_64
- Installs
- Starts
- 0 of 4 features work
- Works offline
Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- monitor uptime of HTTP(s) websites and TCP services
- publish status pages on custom domains
- get downtime alerts via Telegram, Discord or email
An alternative to Uptime Robot and statping.
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its service answers requests
- Replayed from scratch
- Works offline
- Checked on 15 Nov 2026
- Version 2.5.11
Differences the test machine hit
- README: npm run setup, then node server/server.js; Uptime Kuma is now running on http://localhost:3001
In the test: In v2, a first run waits on a database-setup step; with no browser, POST {"dbConfig":{"type":"sqlite"}} to /setup-database first, then create the admin account through the socket.io 'setup' event - README: (no mention of an API)
In the test: Uptime Kuma has no REST API for monitors. A headless socket.io client hung until it sent an Origin header that matches the server URL; no connect_error was printed - README: git clone (master)
In the test: npm run setup checks out the pinned release tag 2.5.11 and downloads a prebuilt dist.tar.gz from GitHub releases (a binary archive, not read)