Updated: 10 November 2026 · Applies to: Uptime Kuma 2.5.9 (official Docker image), nginx and Certbot on Ubuntu 24.04 and 26.04 LTS

To show an Uptime Kuma status page on your own domain, point a DNS record such as status.example.com at the server, add that name under Domain Names in the status page editor, and put a reverse proxy with HTTPS (nginx plus Certbot) in front of Uptime Kuma that passes the Host header. To stop planned work showing as downtime, open Maintenance, click Schedule Maintenance, pick the affected monitors and status pages, and set the time window.

This article used to cover Cachet on Fedora 29, which is long out of support. It now covers Uptime Kuma. If you have not built a status page yet, start with How to Create a Public Status Page with Uptime Kuma, then come back here.

Step 1: Create the DNS record

At your DNS provider, add an A record for status.example.com pointing to the server's IPv4 address (and an AAAA record for IPv6 if the server has one), or a CNAME to the server's hostname. Use a whole domain or subdomain: according to the Uptime Kuma wiki, a subdirectory such as example.com/status is not supported.

Step 2: Add the domain to the status page

  1. Open Status Pages, choose your page and click Edit Status Page.
  2. In the sidebar, find Domain Names and click the plus button next to it (Add a domain).
  3. Type the domain without https://, for example status.example.com.
  4. Click Save.

Uptime Kuma now serves this status page at the root of that domain, based on the Host header of the request. You can test it on the server before DNS has spread (Uptime Kuma listening on 127.0.0.1:3001):

curl -s -o /dev/null -w "%{http_code}\n" -H "Host: status.example.com" http://127.0.0.1:3001/

Output:

200

Any other name still sends / to the dashboard login, which is what you want for your admin address:

curl -s -o /dev/null -w "%{http_code} %{redirect_url}\n" http://127.0.0.1:3001/

Output:

302 http://127.0.0.1:3001/dashboard

You can add several domains to one page, and give each status page its own domain.

Step 3: Add HTTPS with nginx and Certbot

Run Uptime Kuma with its port bound to 127.0.0.1 (for Docker: -p 127.0.0.1:3001:3001) so only the proxy can reach it. Then install nginx and the Certbot nginx plugin from the Ubuntu repositories:

apt update && apt install -y nginx python3-certbot-nginx

Create /etc/nginx/sites-available/uptime-kuma. List the status page domain and, if you want one, a separate name for the dashboard:

server {
    listen 80;
    server_name status.example.com monitor.example.com;

    location / {
        proxy_pass         http://127.0.0.1:3001;
        proxy_http_version 1.1;
        proxy_set_header   Upgrade $http_upgrade;
        proxy_set_header   Connection "upgrade";
        proxy_set_header   Host $host;
        proxy_set_header   X-Real-IP $remote_addr;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header   X-Forwarded-Proto $scheme;
    }
}

The Upgrade and Connection lines are needed because the dashboard uses WebSockets. Host $host is what lets Uptime Kuma pick the right status page for each domain.

Enable the site and check the configuration:

ln -s /etc/nginx/sites-available/uptime-kuma /etc/nginx/sites-enabled/
nginx -t

Output:

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
systemctl reload nginx

Once DNS points to the server, get a free Let's Encrypt certificate. Certbot adds the HTTPS settings to this server block for you:

certbot --nginx -d status.example.com -d monitor.example.com

Finally, in Uptime Kuma open Settings > Reverse Proxy and set Trust Proxy to Yes, then Save. This makes Uptime Kuma trust the X-Forwarded-* headers, so it sees the real visitor IP instead of the proxy's. In our test, domain mapping worked through the Host header with either setting, but a request carrying the domain only in X-Forwarded-Host was matched only after Trust Proxy was set to Yes.

If the domain goes through Cloudflare's proxy, the Uptime Kuma wiki says WebSockets must be enabled in the Cloudflare dashboard.

Step 4: Schedule a maintenance window

During a maintenance window Uptime Kuma marks the chosen monitors as under maintenance instead of down, holds back notifications for them, and shows a notice on the status pages you pick.

  1. Click your profile icon at the top right and choose Maintenance, then Schedule Maintenance.
  2. Enter a Title and a Description (Markdown is supported). Visitors see both on the status page, so write them for customers, for example "Kernel update and reboot".
  3. Under Affected Monitors, pick the monitors that will be interrupted.
  4. Under Status Pages, tick All Status Pages or pick pages under Select status pages.
  5. Choose a Strategy:
    • Single Maintenance Window: one start and end time. Set Start Date/Time and End Date/Time, or use the quick buttons (15 min to 24 hours) to set the end from the start.
    • Recurring - Day of Week: for example every Sunday. Tick the days, set the Maintenance Time Window of a Day (02:00 - 03:00 by default) and, if you like, an Effective Date Range (Optional).
    • Recurring - Day of Month, Recurring - Interval and Cron Expression for other schedules.
    • Active/Inactive Manually: no schedule; you switch it on and off yourself.
  6. Choose the Timezone. The default is Same as Server Timezone. Containers often run in UTC (Settings > General shows the Server Timezone), so pick your own zone, for example Asia/Kolkata, to avoid a window at the wrong hour.
  7. Click Save.

In our test, a single window that had started showed Under Maintenance in the maintenance list, with Pause, Clone, Edit and Delete buttons. On the dashboard the affected monitor's status changed to Maintenance with the message "Monitor under maintenance", and the public status page showed an Under Maintenance box with the title, description and time window. Use Clone to repeat a past window quickly.

Step 5: Post incidents and announcements

For unplanned problems, or news that is not a maintenance window, use an incident post:

  1. Open the status page and click Edit Status Page.
  2. Click Create Incident, fill in Title and Content (Markdown is supported) and choose a style such as info, warning or danger.
  3. Click Post. The message appears at the top of the page.
  4. Update it with Edit, and click Resolve when it is over.

The status page caches results for a few minutes, so a new post can take a short while to appear for visitors; in our test it showed within five minutes.

Where to run it

A status page is most useful when it stays up while your other servers are down, so host it in a different location. An Uptime Kuma VPS gives you root access to set up nginx and Certbot exactly as above. With managed Uptime Kuma hosting, we set up the SSL certificate for your status page domain and you only add one DNS record.

Official documentation: Uptime Kuma wiki: Reverse Proxy, Maintenance and Status Page.

Related services

KVM VPS hosting

NVMe SSD and full root access, with Free Basic Managed Support.

Unmanaged dedicated servers

full root access and free IPMI KVM, with Free Basic Managed Support.

Managed dedicated servers

our engineers look after the server for you, from $135 a month.

Was this answer helpful?

Still stuck? Open a ticket