starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

if you don't create a status page, then nothing works.. #3151

New issue

Open

opened 2026-02-28 03:19:50 -05:00 by deekerman · 15 comments

deekerman commented

2026-02-28 03:19:50 -05:00

Owner

Originally created by @sdetweil on GitHub (Feb 24, 2024).

Originally assigned to: @Angel-Mathew007 on GitHub.

none

🛡️ Security Policy

I agree to have read this project Security Policy

Description

there is doc on status pages
https://github.com/louislam/uptime-kuma/wiki/Status-Page

BUT.. unless you create one, there is NO status page.. not even default
the doc doesn't say that

maybe this changed, I am a recent UK user..

👟 Reproduction steps

install UK (I used dokcer)
start
add a monitor
open the status page

uk/status

nothing.. blank page,
open developers window console, see 404 error

👀 Expected behavior

say something

😓 Actual Behavior

blank screen

🐻 Uptime-Kuma Version

1.23.11

💻 Operating System and Arch

macos arm

🌐 Browser

Chrome V 122.0.6261.69 (Official Build) (arm64)

🖥️ Deployment Environment

Runtime:
Database:
Filesystem used to store the database on:
number of monitors: 1

📝 Relevant log output

none

Originally created by @sdetweil on GitHub (Feb 24, 2024). Originally assigned to: @Angel-Mathew007 on GitHub. ### 📑 I have found these related issues/pull requests none ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description there is doc on status pages https://github.com/louislam/uptime-kuma/wiki/Status-Page BUT.. unless you create one, there is NO status page.. not even default the doc doesn't say that maybe this changed, I am a recent UK user.. ### 👟 Reproduction steps install UK (I used dokcer) start add a monitor open the status page uk/status nothing.. blank page, open developers window console, see 404 error ### 👀 Expected behavior say something ### 😓 Actual Behavior blank screen ### 🐻 Uptime-Kuma Version 1.23.11 ### 💻 Operating System and Arch macos arm ### 🌐 Browser Chrome V 122.0.6261.69 (Official Build) (arm64) ### 🖥️ Deployment Environment - Runtime: - Database: - Filesystem used to store the database on: - number of monitors: 1 ### 📝 Relevant log output ```shell none ```

deekerman added the

A:documentation

bug

good first issue

labels

2026-02-28 03:19:50 -05:00

deekerman commented

2026-02-28 03:19:52 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 24, 2024):

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

@github-actions[bot] commented on GitHub (Apr 24, 2024): We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity. If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@D3dl3g commented on GitHub (May 5, 2024):

config.js

U-T "status/default"

MM Loading

im not using docker, but have it running in server only mode on Debian CT within a Proxmox env

@D3dl3g commented on GitHub (May 5, 2024): config.js ![image](https://github.com/louislam/uptime-kuma/assets/48180011/5d3e457a-162b-476a-9f33-f5a7c7ba56f5) U-T "status/default" ![image](https://github.com/louislam/uptime-kuma/assets/48180011/776ab4fe-63e1-45d8-8a5d-d9994eb56767) MM Loading ![image](https://github.com/louislam/uptime-kuma/assets/48180011/33a6380b-c1cb-4a34-8229-7889374199e1) im not using docker, but have it running in server only mode on Debian CT within a Proxmox env

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@sdetweil commented on GitHub (May 5, 2024):

@D3dl3g yes you misspelled the baseUrl property

@sdetweil commented on GitHub (May 5, 2024): @D3dl3g yes you misspelled the baseUrl property

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@D3dl3g commented on GitHub (May 5, 2024):

I did. Excellent spot. Fixed now and working, mods feel free to delete

@D3dl3g commented on GitHub (May 5, 2024): I did. Excellent spot. Fixed now and working, mods feel free to delete

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@CommanderStorm commented on GitHub (May 5, 2024):

@D3dl3g Please create a new issue next time instead of posting in a semi-random issue (this way we keep the discussion/TODOs on-track)

@CommanderStorm commented on GitHub (May 5, 2024): @D3dl3g Please **create a new issue** next time instead of posting in a semi-random issue (this way we keep the discussion/TODOs on-track)

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@Anurag0218 commented on GitHub (Oct 1, 2024):

is this issue still open? is anyone working on it? If not, can I take it up?

@Anurag0218 commented on GitHub (Oct 1, 2024): is this issue still open? is anyone working on it? If not, can I take it up?

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Oct 1, 2024):

Nobody is working on this to my knowlege.
A contibution would be gretly appreciated ❤️

@CommanderStorm commented on GitHub (Oct 1, 2024): Nobody is working on this to my knowlege. A contibution would be gretly appreciated ❤️

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@ShubhamChavan1 commented on GitHub (Oct 2, 2024):

@CommanderStorm can i work on this ?

@ShubhamChavan1 commented on GitHub (Oct 2, 2024): @CommanderStorm can i work on this ?

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Oct 2, 2024):

Let's give @Anurag0218 a bit of time ^^
There are a lot of other issues out there in this repo. Also it is not nessesary to ask if you can work on an issue..

Just providing a PR is usually fine given the velocity of the project.

@CommanderStorm commented on GitHub (Oct 2, 2024): Let's give @Anurag0218 a bit of time ^^ There are a lot of other issues out there in this repo. Also it is not nessesary to ask if you can work on an issue.. Just providing a PR is usually fine given the velocity of the project.

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@ShubhamChavan1 commented on GitHub (Oct 2, 2024):

@CommanderStorm i am not getting the problem here can please provide more desciption

@ShubhamChavan1 commented on GitHub (Oct 2, 2024): @CommanderStorm i am not getting the problem here can please provide more desciption

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@sdetweil commented on GitHub (Oct 2, 2024):

i described it exactly above

the doc says to open the status page,
but there isn't one by default.

so the doc should say you have to create a status page for UK to access it

@sdetweil commented on GitHub (Oct 2, 2024): i described it exactly above the doc says to open the status page, but there isn't one by default. so the doc should say you have to create a status page for UK to access it

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Oct 2, 2024):

And display a page stating such ("no status pages currently exist. You can create status pages here" with here being a link))

@CommanderStorm commented on GitHub (Oct 2, 2024): And display a page stating such ("no status pages currently exist. You can create status pages here" with here being a link))

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@sdetweil commented on GitHub (Oct 2, 2024):

@CommanderStorm awesome addition!

@sdetweil commented on GitHub (Oct 2, 2024): @CommanderStorm awesome addition!

deekerman commented

2026-02-28 03:19:54 -05:00

Author

Owner

@Angel-Mathew007 commented on GitHub (Oct 8, 2025):