Why does UptimeKuma constantly timeout when the websites are fine and operational? #4164

New issue

Closed

opened 2026-02-28 03:53:22 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 03:53:22 -05:00

Owner

Originally created by @Coysh on GitHub (Jun 11, 2025).

⚠️ Please verify that your question has not already been reported

I have searched the existing issues and found no similar reports.

🛡️ Security Policy

I have read and agree to Uptime Kuma's Security Policy.

📝 Describe your problem

Been having this issue more and more lately. I load a website and it loads in seconds, and I've set most of my montiors to 5 retries and a timeout of 48 seconds.

All my servers are working fine, no load or resource issues and mutliple devices/networks load them fine.

I;m running UptimeKuma on a fly machine with 512MB RAM.

📝 Error Message(s) or Log

2025-06-11T22:02:21Z app[3d8d9347f61758] lhr [info]2025-06-11T23:02:21+01:00 [MONITOR] WARN: Monitor 
    #19 domain1.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 1 | Retry Interval: 60 seconds | Type: http
    2025-06-11T22:02:26Z app[3d8d9347f61758] lhr [info]2025-06-11T23:02:26+01:00 [MONITOR] WARN: Monitor 
    #7 'domain2.com': Pending: timeout of 48000ms exceeded | Max retries: 4 | Retry: 1 | Retry Interval: 30 seconds | Type: http
    2025-06-11T22:03:39Z app[3d8d9347f61758] lhr [info]2025-06-11T23:03:39+01:00 [MONITOR] WARN: Monitor 
    #10 'domain3.com': Pending: timeout of 120000ms exceeded | Max retries: 5 | Retry: 1 | Retry Interval: 300 seconds | Type: http
    2025-06-11T22:03:44Z app[3d8d9347f61758] lhr [info]2025-06-11T23:03:44+01:00 [MONITOR] WARN: Monitor 
    #7 'domain2.com': Pending: timeout of 48000ms exceeded | Max retries: 4 | Retry: 2 | Retry Interval: 30 seconds | Type: http
    2025-06-11T22:03:46Z app[3d8d9347f61758] lhr [info]2025-06-11T23:03:46+01:00 [MONITOR] WARN: Monitor 
    #21 'domain4.com': Pending: timeout of 120000ms exceeded | Max retries: 5 | Retry: 1 | Retry Interval: 300 seconds | Type: http
    2025-06-11T22:04:41Z app[3d8d9347f61758] lhr [info]2025-06-11T23:04:41+01:00 [MONITOR] WARN: Monitor 
    #3 'domain5.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 2 | Retry Interval: 30 seconds | Type: http
    2025-06-11T22:04:42Z app[3d8d9347f61758] lhr [info]2025-06-11T23:04:42+01:00 [MONITOR] WARN: Monitor 
    #1 'domain6.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 1 | Retry Interval: 30 seconds | Type: http
    2025-06-11T22:06:09Z app[3d8d9347f61758] lhr [info]2025-06-11T23:06:09+01:00 [MONITOR] WARN: Monitor 
    #19 domain1.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 1 | Retry Interval: 60 seconds | Type: http
    2025-06-11T22:07:00Z app[3d8d9347f61758] lhr [info]2025-06-11T23:07:00+01:00 [MONITOR] WARN: Monitor 
    #1 'domain6.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 1 | Retry Interval: 30 seconds | Type: http
    2025-06-11T22:07:02Z app[3d8d9347f61758] lhr [info]2025-06-11T23:07:02+01:00 [MONITOR] WARN: Monitor 
    #7 'domain2.com': Pending: timeout of 48000ms exceeded | Max retries: 4 | Retry: 1 | Retry Interval: 30 seconds | Type: http
    2025-06-11T22:07:57Z app[3d8d9347f61758] lhr [info]2025-06-11T23:07:57+01:00 [MONITOR] WARN: Monitor 
    #19 domain1.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 2 | Retry Interval: 60 seconds | Type: http
    2025-06-11T22:07:59Z app[3d8d9347f61758] lhr [info]2025-06-11T23:07:59+01:00 [MONITOR] WARN: Monitor 
    #3 'domain5.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 1 | Retry Interval: 30 seconds | Type: http
    2025-06-11T22:08:18Z app[3d8d9347f61758] lhr [info]2025-06-11T23:08:18+01:00 [MONITOR] WARN: Monitor 
    #1 'domain6.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 2 | Retry Interval: 30 seconds | Type: http
    2025-06-11T22:08:20Z app[3d8d9347f61758] lhr [info]2025-06-11T23:08:20+01:00 [MONITOR] WARN: Monitor #7 'domain2.com': Pending: timeout of 48000ms exceeded | Max retries: 4 | Retry: 2 | Retry Interval: 30 seconds | Type: http

🐻 Uptime-Kuma Version

1.23.18

💻 Operating System and Arch

Fly machine

🌐 Browser

Unknown

🖥️ Deployment Environment

fly machine

Originally created by @Coysh on GitHub (Jun 11, 2025). ### ⚠️ Please verify that your question has not already been reported - [x] I have searched the [existing issues](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc%20) and found no similar reports. ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Describe your problem Been having this issue more and more lately. I load a website and it loads in seconds, and I've set most of my montiors to 5 retries and a timeout of 48 seconds. All my servers are working fine, no load or resource issues and mutliple devices/networks load them fine. I;m running UptimeKuma on a fly machine with 512MB RAM. ### 📝 Error Message(s) or Log ```bash session 2025-06-11T22:02:21Z app[3d8d9347f61758] lhr [info]2025-06-11T23:02:21+01:00 [MONITOR] WARN: Monitor #19 domain1.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 1 | Retry Interval: 60 seconds | Type: http 2025-06-11T22:02:26Z app[3d8d9347f61758] lhr [info]2025-06-11T23:02:26+01:00 [MONITOR] WARN: Monitor #7 'domain2.com': Pending: timeout of 48000ms exceeded | Max retries: 4 | Retry: 1 | Retry Interval: 30 seconds | Type: http 2025-06-11T22:03:39Z app[3d8d9347f61758] lhr [info]2025-06-11T23:03:39+01:00 [MONITOR] WARN: Monitor #10 'domain3.com': Pending: timeout of 120000ms exceeded | Max retries: 5 | Retry: 1 | Retry Interval: 300 seconds | Type: http 2025-06-11T22:03:44Z app[3d8d9347f61758] lhr [info]2025-06-11T23:03:44+01:00 [MONITOR] WARN: Monitor #7 'domain2.com': Pending: timeout of 48000ms exceeded | Max retries: 4 | Retry: 2 | Retry Interval: 30 seconds | Type: http 2025-06-11T22:03:46Z app[3d8d9347f61758] lhr [info]2025-06-11T23:03:46+01:00 [MONITOR] WARN: Monitor #21 'domain4.com': Pending: timeout of 120000ms exceeded | Max retries: 5 | Retry: 1 | Retry Interval: 300 seconds | Type: http 2025-06-11T22:04:41Z app[3d8d9347f61758] lhr [info]2025-06-11T23:04:41+01:00 [MONITOR] WARN: Monitor #3 'domain5.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 2 | Retry Interval: 30 seconds | Type: http 2025-06-11T22:04:42Z app[3d8d9347f61758] lhr [info]2025-06-11T23:04:42+01:00 [MONITOR] WARN: Monitor #1 'domain6.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 1 | Retry Interval: 30 seconds | Type: http 2025-06-11T22:06:09Z app[3d8d9347f61758] lhr [info]2025-06-11T23:06:09+01:00 [MONITOR] WARN: Monitor #19 domain1.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 1 | Retry Interval: 60 seconds | Type: http 2025-06-11T22:07:00Z app[3d8d9347f61758] lhr [info]2025-06-11T23:07:00+01:00 [MONITOR] WARN: Monitor #1 'domain6.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 1 | Retry Interval: 30 seconds | Type: http 2025-06-11T22:07:02Z app[3d8d9347f61758] lhr [info]2025-06-11T23:07:02+01:00 [MONITOR] WARN: Monitor #7 'domain2.com': Pending: timeout of 48000ms exceeded | Max retries: 4 | Retry: 1 | Retry Interval: 30 seconds | Type: http 2025-06-11T22:07:57Z app[3d8d9347f61758] lhr [info]2025-06-11T23:07:57+01:00 [MONITOR] WARN: Monitor #19 domain1.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 2 | Retry Interval: 60 seconds | Type: http 2025-06-11T22:07:59Z app[3d8d9347f61758] lhr [info]2025-06-11T23:07:59+01:00 [MONITOR] WARN: Monitor #3 'domain5.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 1 | Retry Interval: 30 seconds | Type: http 2025-06-11T22:08:18Z app[3d8d9347f61758] lhr [info]2025-06-11T23:08:18+01:00 [MONITOR] WARN: Monitor #1 'domain6.com': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 2 | Retry Interval: 30 seconds | Type: http 2025-06-11T22:08:20Z app[3d8d9347f61758] lhr [info]2025-06-11T23:08:20+01:00 [MONITOR] WARN: Monitor #7 'domain2.com': Pending: timeout of 48000ms exceeded | Max retries: 4 | Retry: 2 | Retry Interval: 30 seconds | Type: http ``` ### 🐻 Uptime-Kuma Version 1.23.18 ### 💻 Operating System and Arch Fly machine ### 🌐 Browser Unknown ### 🖥️ Deployment Environment fly machine

deekerman

2026-02-28 03:53:22 -05:00

closed this issue
added the
help
label

deekerman commented

2026-02-28 03:53:27 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jun 11, 2025):

Not much context to go on.

Could you try our troubleshooting procedure? https://github.com/louislam/uptime-kuma/wiki/Troubleshooting
Could you look if you are being rate limited/... by the service you are checking?

maybe related to cloudflare as suspected in https://github.com/louislam/uptime-kuma/issues/275 ?

@CommanderStorm commented on GitHub (Jun 11, 2025): Not much context to go on. - Could you try our troubleshooting procedure? https://github.com/louislam/uptime-kuma/wiki/Troubleshooting - Could you look if you are being rate limited/... by the service you are checking? maybe related to cloudflare as suspected in https://github.com/louislam/uptime-kuma/issues/275 ?

deekerman commented

2026-02-28 03:53:27 -05:00

Author

Owner

@Coysh commented on GitHub (Jun 12, 2025):

@CommanderStorm - I've looked through #275 and seems like a very similar issue - so I'll close this and continue on that.

@Coysh commented on GitHub (Jun 12, 2025): @CommanderStorm - I've looked through #275 and seems like a very similar issue - so I'll close this and continue on that.