Uptime Kuma Docker Setup: Install, Alerts and Common Fixes

Description and use

Deploy Uptime Kuma in Docker with secure admin access, SQLite persistence, host monitoring, and functional Webhook notifications.

Problem

Deploying Uptime Kuma in Docker while securing the setup and ensuring notifications work correctly.

Outcome

Uptime Kuma successfully deployed with secure admin access, SQLite persistence, host‑based monitoring, and functional Webhook notifications.

Workflow

• Create project folder and download compose.yaml
• Modify compose.yaml to bind port to 127.0.0.1:3001 if using reverse proxy
• Run docker compose up -d and check logs
• Open http://<server>:3001 and complete setup wizard selecting SQLite and creating admin account
• Add an HTTP monitor pointing to a host service using host.docker.internal or network gateway IP
• Create a Webhook notification pointing to a host listener, enable Default enabled or Apply on all existing monitors
• Test notification and verify alerts on monitor state changes

Evidence

Start louislam/uptime-kuma:2.5.6 with the official compose file. If a reverse proxy goes in front, bind the port to 127.0.0.1:3001, and either way create the admin account right after the first start.

Source

Keep ./data on a local disk, not NFS or SMB.

Source

A notification only fires for monitors it's attached to, so turn on Default enabled or Apply on all existing monitors.

Source