How to set uptime-kuma to run on subdomain resource? #4039

Closed
opened 2026-02-28 03:49:04 -05:00 by deekerman · 1 comment
Owner

Originally created by @hpandelo on GitHub (Mar 18, 2025).

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I've set a subdomain like monitoring.<company>.com/uptime to uptime-kuma
Nginx looks like:

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

I've set the BASE_PATH env var

 docker inspect uptime-kuma | grep BASE_PATH
                "BASE_PATH=/uptime",

I've set the "Primary Base URL" on settings as like:
https://monitoring.<company>.com/uptime

But it's still redirecting to /dashboard instead of /uptime/dashboard and If I try to enforce via nginx config, just a blank screen appears (probably not fetching all files)

Via HTTP protocol using IP:Port or subdomain:Port, it works

Note: It works in parallel with other applications, so I don't want to set it on root of the subdomain

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

louislam/uptime-kuma:1

💻 Operating System and Arch

Ubuntu 24

🌐 Browser

any

🖥️ Deployment Environment

  • Runtime: Docker version 28.0.1, build 068a01e
  • Database:
  • Filesystem used to store the database on:
  • number of monitors:
Originally created by @hpandelo on GitHub (Mar 18, 2025). ### ⚠️ Please verify that this question has NOT been raised before. - [x] I checked and didn't find similar issue ### 🛡️ Security Policy - [x] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I've set a subdomain like `monitoring.<company>.com/uptime` to uptime-kuma Nginx looks like: ```yml location /uptime/ { proxy_pass http://127.0.0.1:3001/; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } ``` I've set the BASE_PATH env var ```sh docker inspect uptime-kuma | grep BASE_PATH "BASE_PATH=/uptime", ``` I've set the "Primary Base URL" on settings as like: `https://monitoring.<company>.com/uptime` But it's still redirecting to `/dashboard` instead of `/uptime/dashboard` and If I try to enforce via nginx config, just a blank screen appears (probably not fetching all files) Via HTTP protocol using IP:Port or subdomain:Port, it works Note: It works in parallel with other applications, so I don't want to set it on root of the subdomain ### 📝 Error Message(s) or Log _No response_ ### 🐻 Uptime-Kuma Version louislam/uptime-kuma:1 ### 💻 Operating System and Arch Ubuntu 24 ### 🌐 Browser any ### 🖥️ Deployment Environment - Runtime: Docker version 28.0.1, build 068a01e - Database: - Filesystem used to store the database on: - number of monitors:
deekerman 2026-02-28 03:49:04 -05:00
  • closed this issue
  • added the
    help
    label
Author
Owner

@felipecrs commented on GitHub (Mar 18, 2025):

@hpandelo I suggest you close it as duplicate of https://github.com/louislam/uptime-kuma/issues/147.

@felipecrs commented on GitHub (Mar 18, 2025): @hpandelo I suggest you close it as duplicate of https://github.com/louislam/uptime-kuma/issues/147.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#4039
No description provided.