starred/uptime-kuma

Fork 0

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

Status page not reflecting monitor state #1148

New issue

Closed

opened 2026-02-28 02:11:34 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:11:34 -05:00

Owner

Originally created by @Coolie1101 on GitHub (Jun 7, 2022).

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

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

Monitors on status page (http://192.168.200.209:3001/status/test) does not reflect the status on the monitors on the dashboard.

👟 Reproduction steps

Create status page and add monitors.

👀 Expected behavior

Both dashboard and status page monitor stats should be the same.

😓 Actual Behavior

Paused monitors in dashboard shows as online in status page.

🐻 Uptime-Kuma Version

1.16.1

💻 Operating System and Arch

Raspbian 10 (buster)

🌐 Browser

Google Chrome 102.0.5005.63

🐋 Docker Version

Docker 20.10.16, build aa7e414

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @Coolie1101 on GitHub (Jun 7, 2022). ### ⚠️ Please verify that this bug 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) ### Description Monitors on status page (http://192.168.200.209:3001/status/test) does not reflect the status on the monitors on the dashboard. ### 👟 Reproduction steps Create status page and add monitors. ### 👀 Expected behavior Both dashboard and status page monitor stats should be the same. ### 😓 Actual Behavior Paused monitors in dashboard shows as online in status page. ### 🐻 Uptime-Kuma Version 1.16.1 ### 💻 Operating System and Arch Raspbian 10 (buster) ### 🌐 Browser Google Chrome 102.0.5005.63 ### 🐋 Docker Version Docker 20.10.16, build aa7e414 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_

deekerman

2026-02-28 02:11:34 -05:00

closed this issue
added the
bug
label

deekerman commented

2026-02-28 02:11:39 -05:00

Author

Owner

@daeho-ro commented on GitHub (Jun 11, 2022):

I think the status page is for the public, so the status should be up or down only whenever the monitoring is paused or not.

@daeho-ro commented on GitHub (Jun 11, 2022): I think the status page is for the public, so the status should be up or down only whenever the monitoring is paused or not.

deekerman commented

2026-02-28 02:11:39 -05:00

Author

Owner

@Computroniks commented on GitHub (Jun 11, 2022):

I think the status page is for the public, so the status should be up or down only whenever the monitoring is paused or not.

Yes, this is correct. Currently, if a monitor is paused, the status is shown as the last heartbeat before it was paused. I think that this is the best solution as I am not sure if it should be public that a monitor is paused.

@Computroniks commented on GitHub (Jun 11, 2022): > I think the status page is for the public, so the status should be up or down only whenever the monitoring is paused or not. Yes, this is correct. Currently, if a monitor is paused, the status is shown as the last heartbeat before it was paused. I think that this is the best solution as I am not sure if it should be public that a monitor is paused.

deekerman commented

2026-02-28 02:11:39 -05:00

Author

Owner

@Coolie1101 commented on GitHub (Jun 11, 2022):

I think the status page is for the public

I think that this is the best solution as I am not sure if it should be public that a monitor is paused.

Makes sense, thanks.

@Coolie1101 commented on GitHub (Jun 11, 2022): > I think the status page is for the public > I think that this is the best solution as I am not sure if it should be public that a monitor is paused. Makes sense, thanks.

deekerman referenced this issue

2026-02-28 03:20:51 -05:00

Gotify throws out error when sending down notification #3184

deekerman referenced this issue

2026-02-28 03:20:55 -05:00

Gotify throws out error when sending down notification #3184

deekerman referenced this issue

2026-02-28 03:20:56 -05:00

Gotify throws out error when sending down notification #3184