Guides ยท Oct 5, 2026
Self-Host Uptime Kuma on a VPS for Website and Server Monitoring
Install Uptime Kuma with Docker on a VPS, add HTTP, ping and port monitors, set up alerts to Discord or email, and monitor backup jobs with push monitors.
If your site, bot or game server goes down at 3 a.m., you want to hear about it from a monitor, not from an angry user. Uptime Kuma is a free, open-source monitoring tool with a clean web interface. It checks websites, ports, ping and more on a schedule and sends alerts to Discord, Telegram, email and many other channels. This guide installs it with Docker on a VPS.
One important design point: do not run your monitor on the server it watches. If that server dies, the monitor dies with it and nobody gets told. Put Uptime Kuma on a separate small server, ideally in a different location. A cheap VPS in Oregon watching servers in Virginia (or the other way round) is a good setup.
Requirements
- An Ubuntu or Debian server with Docker installed. If you need it, follow the Docker installation guide.
- A domain or subdomain pointing at the server if you want HTTPS (for example
status.example.com). - About 1 GB of RAM is enough for a modest number of monitors.
1. Create a Compose file
mkdir -p ~/uptime-kuma && cd ~/uptime-kuma
nano compose.yaml
services:
uptime-kuma:
image: louislam/uptime-kuma:1
container_name: uptime-kuma
restart: unless-stopped
ports:
- "127.0.0.1:3001:3001"
volumes:
- ./data:/app/data
The port is bound to 127.0.0.1 on purpose, so the dashboard is not exposed directly. You will put a reverse proxy with HTTPS in front. Check the project's page for the current recommended image tag before you deploy, since major versions change.
docker compose up -d
docker compose logs -f
2. Add HTTPS with a reverse proxy
The simplest option is Caddy, which gets certificates automatically:
sudo apt install -y caddy
sudo nano /etc/caddy/Caddyfile
status.example.com {
reverse_proxy 127.0.0.1:3001
}
sudo systemctl reload caddy
sudo ufw allow 80,443/tcp
Uptime Kuma uses WebSockets, and Caddy handles them without extra configuration. If you prefer Nginx, our Nginx reverse proxy guide shows the certificate steps and the WebSocket headers.
Open https://status.example.com and create the admin account immediately, because the first visitor sets it up.
3. Add your first monitors
Click Add New Monitor and choose the type:
- HTTP(s): checks that a URL returns a good status code. Enter the address and set the interval (60 seconds is a common choice). Use a keyword monitor if you need to check that specific text is on the page.
- TCP Port: checks that a service accepts connections, such as a Minecraft server on 25565, a database port or SSH.
- Ping: basic reachability for a server.
- Docker container and DNS monitors are also available.
For a Discord bot, monitor its health endpoint if it has one (see the bot hosting guide), or use a push monitor described below.
4. Set up notifications
Go to Settings, Notifications and set up at least one channel you actually watch:
- Discord: create a webhook in a channel (Channel settings, Integrations, Webhooks) and paste the URL.
- Telegram: create a bot with BotFather and add the token and chat ID.
- Email (SMTP): use your mail provider's SMTP details.
Use the test button, and enable the notification on your monitors. Treat the webhook URL like a password: anyone who has it can post to your channel.
Tune retries so that you are not woken by a single dropped packet: setting Retries to 2 or 3 means a monitor must fail repeatedly before alerting.
5. Push monitors for cron jobs and backups
A Push monitor works in reverse: Uptime Kuma gives you a URL, and your job calls it when it succeeds. If the call does not arrive within the expected time, you get an alert. This is ideal for backups:
restic backup /etc /opt && curl -fsS "https://status.example.com/api/push/YOUR_TOKEN?status=up&msg=OK" > /dev/null
Add that to the end of your backup script (see the restic backup guide). If the backup fails or the server is down, the call never happens, and you are alerted.
6. A public status page
Under Status Pages you can create a page listing selected monitors, which is useful for communities and customers. Choose which monitors to show and map a custom domain if you like. Do not include monitors that reveal internal hostnames you want to keep private.
7. Updating and backing up Uptime Kuma
cd ~/uptime-kuma
docker compose pull
docker compose up -d
docker image prune -f
All settings live in ./data. Include that folder in your backups. Before a major version upgrade, copy the folder and read the project's release notes.
Monitoring tips
- Monitor what users experience, not just whether the server answers ping. A server can respond to ping while the web app is broken.
- Keep intervals reasonable. Checking every 20 seconds from one small server is rarely worth it.
- Test your alerts by stopping a test service on purpose.
- Remember attacks. A downtime alert plus a DDoS alert from your provider tells you quickly whether you are dealing with a crash or an attack. See how DDoS protection works.
Frequently asked questions
Can I run Uptime Kuma on the same server I monitor?
You can, but you will not be alerted if that server goes down. Run it on a separate server, ideally in a different location.
How much RAM does Uptime Kuma need?
It is lightweight. A small server with around 1 GB of RAM handles a modest number of monitors, but check usage as you add more.
Can it monitor game servers?
Yes. Use a TCP port monitor on the game port to see whether the server accepts connections.
Does it send alerts to Discord?
Yes. Create a webhook in your Discord channel and add it as a notification in Uptime Kuma.
Related guides
- How to Install Docker and Docker Compose on a VPS
- Automated Encrypted VPS Backups with restic (Step by Step)
- How to Host a Discord Bot 24/7 on a VPS (Node.js & Python)
Need a server for this?
Every TidalVPS VPS comes with full root access, unmetered traffic, daily backups and DDoS protection.