starred/uptime-kuma

Fork 0

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

get 200 but found 404 #3918

New issue

Closed

opened 2026-02-28 03:45:05 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 03:45:05 -05:00

Owner

Originally created by @maxzhang2017 on GitHub (Jan 20, 2025).

Related to issue #3277

🛡️ Security Policy

I agree to have read this project Security Policy

Description

Below is the log of uptime.
[MONITOR] WARN: Monitor #18 'www.xxx.com': Pending: Request failed with status code 404 | Max retries: 3 | Retry: 1 | Retry Interval: 20 seconds | Type: http

But I checked nginx log and the status code is always 200.

👟 Reproduction steps

I can't, in one day ( check every minitue) this happened about 70 times

👀 Expected behavior

get 200

😓 Actual Behavior

In a few cases get 404

🐻 Uptime-Kuma Version

1.23.15

💻 Operating System and Arch

k8s

🌐 Browser

Firefox

🖥️ Deployment Environment

Runtime: v1.24.6-aliyun.1
Database: sqlite
Filesystem used to store the database on: local file
number of monitors: about 40

📝 Relevant log output

Originally created by @maxzhang2017 on GitHub (Jan 20, 2025). ### 📑 I have found these related issues/pull requests Related to issue #3277 ### 🛡️ Security Policy - [x] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description Below is the log of uptime. [MONITOR] WARN: Monitor #18 'www.xxx.com': Pending: Request failed with status code 404 | Max retries: 3 | Retry: 1 | Retry Interval: 20 seconds | Type: http But I checked nginx log and the status code is always 200. ### 👟 Reproduction steps I can't, in one day ( check every minitue) this happened about 70 times ### 👀 Expected behavior get 200 ### 😓 Actual Behavior In a few cases get 404 ### 🐻 Uptime-Kuma Version 1.23.15 ### 💻 Operating System and Arch k8s ### 🌐 Browser Firefox ### 🖥️ Deployment Environment Runtime: v1.24.6-aliyun.1 Database: sqlite Filesystem used to store the database on: local file number of monitors: about 40 ### 📝 Relevant log output ```shell ```

deekerman

2026-02-28 03:45:05 -05:00

closed this issue
added the
Stale

help
labels

deekerman commented

2026-02-28 03:45:11 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 21, 2025):

I think you are catching a real issue there.
Where the issue is coming from is really hard to diagnose from a far without any information about your setup

@CommanderStorm commented on GitHub (Jan 21, 2025): I think you are catching a real issue there. Where the issue is coming from is really hard to diagnose from a far without any information about your setup

deekerman commented

2026-02-28 03:45:12 -05:00

Author

Owner

@maxzhang2017 commented on GitHub (Jan 21, 2025):

Yeah, it's weird. But I don't know how to reproduce it, it's always normal, it becomes abnormal at some point, but not every check is abnormal, about 6% of the time it will be abnormal.

@maxzhang2017 commented on GitHub (Jan 21, 2025): Yeah, it's weird. But I don't know how to reproduce it, it's always normal, it becomes abnormal at some point, but not every check is abnormal, about 6% of the time it will be abnormal.

deekerman commented

2026-02-28 03:45:12 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 23, 2025):

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 (Mar 23, 2025): 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.