Deploy Uptime Kuma
A fancy self-hosted monitoring tool.
⭐ 55.0k stars📜 MIT🔴 Advanced⏱ ~20 minutes
What You’ll Get
A fully working Uptime Kuma instance running on your server. Your data stays on your hardware — no third-party access, no usage limits, no surprise invoices.
Prerequisites
- A server with Docker and Docker Compose installed (setup guide)
- A domain name pointed to your server (optional but recommended)
- Basic terminal access (SSH)
The Config
Create a directory for Uptime Kuma and add this docker-compose.yml:
# -------------------------------------------------------------------------
# 🚀 Created and distributed by The AltStack
# 🌍 https://thealtstack.com
# -------------------------------------------------------------------------
# Docker Compose for Uptime Kuma
version: '3.8'
services:
uptime-kuma:
image: louislam/uptime-kuma:1 # Official image is standard
container_name: uptime-kuma
ports:
- "3001:3001"
volumes:
- uptime_kuma_data:/app/data
networks:
- uptime_net
healthcheck:
test: [ "CMD", "curl", "-f", "http://localhost:3001/" ]
interval: 30s
timeout: 10s
retries: 3
restart: unless-stopped
networks:
uptime_net:
driver: bridge
volumes:
uptime_kuma_data:
name: uptime_kuma_dataLet’s Ship It
# Create a directory
mkdir -p /opt/uptime-kuma && cd /opt/uptime-kuma
# Create the docker-compose.yml (paste the config above)
nano docker-compose.yml
# Pull images and start
docker compose up -d
# Watch the logs
docker compose logs -fPost-Deployment Checklist
- Service is accessible on the configured port
- Admin account created (if applicable)
- Reverse proxy configured (Caddy guide)
- SSL/HTTPS working
- Backup script set up (backup guide)
- Uptime monitor added (Uptime Kuma)
The “I Broke It” Section
Container won’t start?
docker compose logs uptime-kuma | tail -50Port already in use?
# Find what's using the port
lsof -i :PORT_NUMBERNeed to start fresh?
docker compose down -v # ⚠️ This deletes volumes/data!
docker compose up -d