louislam/uptime-kuma

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

Open

#4523 opened on Feb 24, 2024

View on GitHub
 (15 comments) (0 reactions) (1 assignee)JavaScript (86,760 stars) (7,844 forks)batch import
A:documentationbuggood first issue

Description

📑 I have found these related issues/pull requests

none

🛡️ 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

Contributor guide

Tech stack
javascriptnodejs
Domain
documentationfrontend
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
Check the Uptime Kuma wiki page for Status Page (https://github.com/louislam/uptime kuma/wiki/Status Page) and confirm the missing instructions. Add a note that a status page must be created first, and consider adding a default or a prompt. Also review the status page code (e.g., src/pages/StatusPage.vue) to see if a fallback message can be shown when no status page exists.