# Uptime Kuma Status Page

> Self-hosted uptime monitoring with beautiful status pages, multiple notification channels, and ntfy for push notifications to your devices.

- Category: Monitoring & Observability
- Difficulty: beginner
- Components: uptime-kuma, ntfy
- Tags: uptime, status-page, monitoring, alerts, notifications
- Source: https://docker.recipes/monitoring/uptimekuma-statuspage

## Overview

Uptime Kuma is a self-hosted monitoring solution that provides comprehensive service availability tracking with beautiful, customizable status pages. Originally created as an open-source alternative to commercial services like Uptime Robot, it supports over 20 monitor types including HTTP/HTTPS, TCP, Ping, DNS Record, Push, Steam Game Server, and Docker Container monitoring. The tool has gained significant popularity in the homelab and small business communities due to its extensive feature set and zero licensing costs.

This stack combines Uptime Kuma with ntfy, a simple HTTP-based pub-sub notification service that delivers real-time push notifications to mobile devices without requiring complex setup or third-party dependencies. While Uptime Kuma supports over 90 notification channels including Slack, Discord, and email, ntfy provides instant mobile alerts through a lightweight, self-hosted solution. The integration allows you to receive immediate notifications when services go down, certificates expire, or performance thresholds are exceeded.

This combination is ideal for system administrators, DevOps teams, and homelab enthusiasts who want complete control over their monitoring infrastructure without monthly subscription fees. Unlike cloud-based alternatives, this stack provides unlimited monitors, custom check intervals, and the ability to monitor internal services behind firewalls, making it perfect for organizations that prioritize data privacy and cost control.

## Features

- Over 20 monitor types including HTTP/HTTPS, TCP, Ping, DNS, Push, Steam Game Server, and Docker Container monitoring
- Beautiful, responsive status pages with custom branding, logos, and themes for public or private use
- Certificate expiry monitoring with configurable advance warning notifications
- Multi-language support with translations for over 30 languages
- Two-factor authentication (2FA) support for enhanced security
- Instant mobile push notifications through ntfy without requiring third-party services or API keys
- Flexible notification rules with maintenance windows, alert grouping, and escalation policies
- Proxy support for monitoring services through HTTP/HTTPS/SOCKS proxies

## Use cases

- Small businesses creating public status pages to communicate service availability to customers
- Homelab enthusiasts monitoring self-hosted services like Plex, Nextcloud, and NAS devices
- DevOps teams tracking internal microservices and API endpoints behind corporate firewalls
- Web developers monitoring client websites with custom check intervals and maintenance windows
- System administrators setting up certificate expiry monitoring for SSL/TLS certificates
- IT departments creating internal dashboards to track server uptime and network connectivity
- Freelancers and agencies providing uptime monitoring services to multiple clients from a single dashboard

## Prerequisites

- Docker and Docker Compose installed on your host system
- Minimum 256MB RAM available for Uptime Kuma container operations
- Ports 3001 and 8080 available on your host system (configurable via environment variables)
- Basic understanding of HTTP monitoring concepts and notification workflows
- Mobile device with ntfy app installed for receiving push notifications
- Network access to the services you want to monitor from the container host

## docker-compose.yml

```yaml
services:
  uptime-kuma:
    image: louislam/uptime-kuma:latest
    container_name: uptime-kuma
    restart: unless-stopped
    volumes:
      - uptime_data:/app/data
    ports:
      - "${KUMA_PORT:-3001}:3001"

  ntfy:
    image: binwiederhier/ntfy:latest
    container_name: kuma-ntfy
    restart: unless-stopped
    command: serve
    ports:
      - "${NTFY_PORT:-8080}:80"
    volumes:
      - ntfy_cache:/var/cache/ntfy
    environment:
      - TZ=${TZ:-UTC}

volumes:
  uptime_data:
  ntfy_cache:
```

## .env

```bash
# Uptime Kuma Configuration
KUMA_PORT=3001
TZ=UTC

# Ntfy Push Notifications
NTFY_PORT=8080
```

## Usage notes

- Access Uptime Kuma at http://localhost:3001
- Create an admin account on first access
- Ntfy push notification server at http://localhost:8080
- In Uptime Kuma, add ntfy notification: http://ntfy/your-topic
- Subscribe to ntfy topics on your phone for instant alerts
- Create public status pages to share service health

## Troubleshooting

- Uptime Kuma shows 'Cannot connect to database': Check that the uptime_data volume has proper permissions and sufficient disk space available
- ntfy notifications not working: Verify the ntfy container URL in Uptime Kuma notifications uses 'http://ntfy' (container name) not 'localhost'
- Mobile app not receiving notifications: Ensure you're subscribed to the exact topic name configured in Uptime Kuma and ntfy container is accessible
- Status page shows 'Down' for internal services: Check Docker network connectivity and ensure monitored services are accessible from the uptime-kuma container
- Certificate monitoring fails: Verify the target service uses valid SSL/TLS certificates and the monitoring interval allows sufficient time for SSL handshake
- High memory usage on Uptime Kuma: Reduce check frequency for monitors or increase container memory limits if monitoring many services simultaneously

