Deploying Uptime Kuma - Self-Hosted Status Page and Monitoring Tool

Uptime Kuma is an open-source monitoring solution that can track the availability of various services such as websites, APIs, TCP ports, DNS records, and more. This guide outlines the steps to deploy Uptime Kuma on a Linux server using Docker Compose, secured by a Traefik reverse proxy. Upon completion, a working Uptime Kuma instance will be accessible with an active monitor, a notification channel, and a public status page.

To begin, ensure you have a Linux-based server with non-root sudo privileges, Docker, and Docker Compose installed. Additionally, create a domain A record pointing to the server's public IP address. Grant your user Docker permissions and start a new shell session to apply the changes.

Next, create the necessary directory structure and environment variables. Begin by creating a project directory, entering it, and then creating a directory for persistent Uptime Kuma data. Generate a .env file and add the required variables, including the domain name and email address for Let's Encrypt certificate notifications.

Deploy Uptime Kuma and Traefik as separate containers using Docker Compose. Configure Traefik to handle TLS termination and forwarding of requests to Uptime Kuma, while Uptime Kuma operates in a separate Docker network. Start the services in detached mode and verify their successful startup.

Log in to Uptime Kuma using the domain specified in the .env file. Upon the first login, create an administrator account and add a new monitor for the service you want to track. After setting up the monitor, configure a notification channel to receive alerts when the monitored service's status changes.

With these steps completed, Uptime Kuma will now actively monitor the specified service and notify you of any status changes via the configured notification channel.