Engineering notes

Run Uptime Kuma on a UK VPS: install, HTTPS with Caddy, and backups

How to run Uptime Kuma on its own small VPS so it can tell you when your other servers are down. Sizing, the official Docker Compose install bound to localhost, Caddy for HTTPS, firewall rules and backups.

By Vozora · Published

Uptime Kuma describes itself as "an easy-to-use self-hosted monitoring tool" (Uptime Kuma README, checked 2026-11-18). It checks websites, ports, DNS records, Docker containers and more on an interval, keeps a history, and sends alerts through email, Telegram, Discord, Slack and "90+ notification services". It also serves public status pages.

It suits anyone running a few services who wants to hear about an outage before their users do, without paying per monitor.

The one rule that matters more than any setting: run it somewhere other than what it watches. A monitor on the server it checks goes down with that server and tells you nothing. So this guide puts Uptime Kuma on its own small server. The commands follow Uptime Kuma's README and wiki, Caddy's install page and Docker's install pages as we read them on 18 November 2026. We have not run this exact sequence on a Vozora server, so read each step against the linked page first.

What it needs

Uptime Kuma's README publishes no minimum RAM, CPU or disk. It lists "Major Linux distros such as Debian, Ubuntu, Fedora and ArchLinux" as supported, and warns that "File Systems like NFS (Network File System) are NOT supported. Please map to a local directory or volume."

We ran it in Docker on a 1 GB server for our new VPS checklist without trouble, but we did not record its memory, so we have no figure to quote. Memory grows with the number of monitors and how long history is kept. After a day of real checks, sudo docker stats --no-stream gives you the number for your setup.

Vozora size: Nano (1 vCPU, 2 GB RAM, 30 GB disk). Enough for Uptime Kuma, Caddy and a long monitor list. Specifications and current rates are on the pricing page. Pick Ubuntu 24.04 or Debian 12 when you create the server.

If the services you watch are on other Vozora servers, put the Kuma server in the same private network as them. It can then check internal ports, such as a database or an admin panel bound to the private address, that you would never open to the internet.

Install Docker

Uptime Kuma's recommended install is Docker. Docker's install pages for Ubuntu and Debian (checked 2026-11-18) give the same steps apart from the word ubuntu or debian in two URLs and the codename. This version reads both from /etc/os-release, so it works on either Vozora image:

. /etc/os-release
sudo apt update
sudo apt install -y ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/$ID/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc
sudo tee /etc/apt/sources.list.d/docker.sources <<EOF
Types: deb
URIs: https://download.docker.com/linux/$ID
Suites: ${UBUNTU_CODENAME:-$VERSION_CODENAME}
Components: stable
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/docker.asc
EOF
sudo apt update
sudo apt install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

Install Uptime Kuma

The README's Docker Compose install is four lines:

mkdir uptime-kuma
cd uptime-kuma
curl -o compose.yaml https://raw.githubusercontent.com/louislam/uptime-kuma/master/compose.yaml
docker compose up -d

Run the first three, but change one line before the fourth. The compose.yaml it fetches, as published on the day we checked, is:

services:
  uptime-kuma:
    image: louislam/uptime-kuma:2
    restart: unless-stopped
    volumes:
      - ./data:/app/data
    ports:
      # <Host Port>:<Container Port>
      - "3001:3001"

The README says that after this, "Uptime Kuma is now running on all network interfaces". On a VPS that means port 3001 is open to the internet over plain HTTP, and Docker's documentation says traffic to published ports "gets diverted before it goes through the ufw firewall settings" (Docker docs, packet filtering and firewalls, checked 2026-11-18), so a host firewall will not stop it. The README gives the fix for the docker run form: "If you want to limit exposure to localhost only", publish on 127.0.0.1:3001:3001. Do the same in the Compose file:

    ports:
      - "127.0.0.1:3001:3001"

Then start it:

sudo docker compose up -d
sudo docker compose ps

The data lives in ./data next to the Compose file, on the server's own disk, which is what the NFS warning asks for.

Create the admin account over an SSH tunnel

A new Uptime Kuma asks whoever opens it first to create the admin account. Do that before it is reachable from the internet. From your own machine:

ssh -N -L 3001:127.0.0.1:3001 ubuntu@<server-ip>

(Use debian@ on the Debian image.) Open http://localhost:3001 in your browser and create the account. The README lists 2FA support; turn it on in the settings while you are there.

HTTPS with Caddy

Uptime Kuma's wiki recommends a reverse proxy to expose it, and notes that "Uptime Kuma is based on WebSocket", so the proxy must pass WebSocket upgrades. It also says it "does not support a subdirectory", so give it its own name, such as status.example.com (Uptime Kuma wiki, reverse proxy, checked 2026-11-18). Caddy handles both the certificate and WebSockets without extra settings.

Point an A record for the name at the server's IPv4 address, and an AAAA record at its IPv6 address if you want it reachable over IPv6. Vozora hosts DNS free if you want it there.

Install Caddy from its own repository, as Caddy's install page gives it for Debian and Ubuntu (checked 2026-11-18):

sudo apt install --yes debian-keyring debian-archive-keyring apt-transport-https curl
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo chmod o+r /usr/share/keyrings/caddy-stable-archive-keyring.gpg
sudo chmod o+r /etc/apt/sources.list.d/caddy-stable.list
sudo apt update
sudo apt install caddy

Replace /etc/caddy/Caddyfile with the wiki's Caddy example, using your name:

status.example.com {
    reverse_proxy 127.0.0.1:3001
}
sudo caddy validate --config /etc/caddy/Caddyfile
sudo systemctl reload caddy

Caddy requests the certificate on first load. Then, in Uptime Kuma's settings under Reverse Proxy, the wiki suggests setting Trust Proxy to Yes when Kuma is only reachable through the proxy, so logs show the real client address.

Firewall and SSH

In the server's Vozora firewall:

  • TCP 80 and 443 from 0.0.0.0/0, and from ::/0 if you added an AAAA record. IPv4 and IPv6 rules are separate.
  • TCP 22 from your own address only, if you have a fixed one.
  • Nothing for 3001. It is bound to 127.0.0.1 anyway.

New servers start in the default firewall, which allows all traffic, so replace its allow-everything rules with these. Log in with your SSH key as the image's user, and prove passwords are refused with ssh -o PubkeyAuthentication=no, as in the new VPS checklist.

If only you use the dashboard, you can skip Caddy entirely and keep using the SSH tunnel above. Public status pages are the main reason to expose it.

What to monitor

  • Each public URL, with the HTTP(s) Keyword monitor, so a proxy error page does not count as up.
  • Certificate expiry. The README lists "Certificate info" among the features; set a notification well before expiry.
  • Your backups, with a Push monitor: the backup script calls a URL when it finishes, and Kuma alerts when the call does not arrive.
  • This server itself, from somewhere else. A free external check on the status page's URL is enough; something has to notice if the monitor goes down.

Backups

Everything Uptime Kuma keeps is in ./data. Back it up with the container stopped, so the database is not mid-write:

cd ~/uptime-kuma
sudo docker compose stop
sudo tar czf ~/uptime-kuma-data-$(date +%F).tar.gz data
sudo docker compose start

Copy the archive and compose.yaml off the server, with restic on a timer as in our self-hosting guide, or just with scp to your own machine. The archive includes notification settings, which can contain tokens for your chat and email accounts.

Vozora's backups give you a whole-disk copy too: turn on daily backups (taken each night, newest 7 kept), and press Back up now before upgrading Uptime Kuma. They are stored on the same platform as the server, so keep the off-server copy as well.

Short version

  1. A Nano, separate from the servers it watches, in their private network if they have one.
  2. Docker from Docker's repository; Uptime Kuma's compose.yaml, with the port changed to 127.0.0.1:3001:3001.
  3. Create the admin account over ssh -L, and turn on 2FA.
  4. Caddy in front with its own hostname; Vozora firewall with 80 and 443 open and nothing on 3001.
  5. Stop, archive ./data, start; keep it off the server; daily Vozora backups as well.

A Vozora server is billed by the minute from prepaid credit while it exists, including while stopped. Sizes and prices are on the pricing page. For things worth watching with it, see n8n on a UK VPS, Coolify on a UK VPS and a WireGuard VPN server on a UK VPS.

© 2026 Vozora. A trading name of Bankside Technology Ltd, registered in England and Wales, company no. 17253446. Registered office: First Floor, Swan Buildings, 20 Swan Street, Manchester, England, M4 5JW.