uptime-kuma: Check of running Websites results in error "maxContentLength size of -1 exceeded"
⚠️ 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
Hi,
i’m trying to monitor some websites (that are definitely up) but keep receiving an error “maxContentLength size of -1 exceeded”. Thank you for your help
👟 Reproduction steps
Add new Monitor -> HTTP(S) -> *put in whatever * -> save
👀 Expected behavior
Not to receive an error of any kind, Host being up
😓 Actual Behavior
Error: “maxContentLength size of -1 exceeded”
🐻 Uptime-Kuma Version
1.18.5
💻 Operating System and Arch
Hypervisor: Proxmox Virtual Environment 7.2-11 Virtual Machine: Ubuntu 22.04.1 LTS Kernel: Linux 5.15.60-2-pve
🌐 Browser
Brave 1.44.112 (Chromium 106.0.5249.119)
🐋 Docker Version
20.10.20
🟩 NodeJS Version
No response
📝 Relevant log output
docker logs uptime-kuma
[...]
2022-10-20T13:18:11.703Z [MONITOR] WARN: Monitor #7 'web': Pending: maxContentLength size of -1 exceeded | Max retries: 10 | Retry: 1 | Retry Interval: 60 seconds | Type: http
2022-10-20T13:19:46.563Z [MONITOR] WARN: Monitor #6 'Gitea': Pending: maxContentLength size of -1 exceeded | Max retries: 10 | Retry: 7 | Retry Interval: 60 seconds | Type: http
2022-10-20T13:19:59.942Z [MONITOR] WARN: Monitor #7 'web': Pending: maxContentLength size of -1 exceeded | Max retries: 10 | Retry: 2 | Retry Interval: 60 seconds | Type: http
2022-10-20T13:21:34.661Z [MONITOR] WARN: Monitor #6 'Gitea': Pending: maxContentLength size of -1 exceeded | Max retries: 10 | Retry: 8 | Retry Interval: 60 seconds | Type: http
2022-10-20T13:21:48.133Z [MONITOR] WARN: Monitor #7 'web': Pending: maxContentLength size of -1 exceeded | Max retries: 10 | Retry: 3 | Retry Interval: 60 seconds | Type: http
2022-10-20T13:23:22.753Z [MONITOR] WARN: Monitor #6 'Gitea': Pending: maxContentLength size of -1 exceeded | Max retries: 10 | Retry: 9 | Retry Interval: 60 seconds | Type: http
2022-10-20T13:23:26.475Z [MONITOR] INFO: Get Monitor: 6 User ID: 1
2022-10-20T13:25:10.884Z [MONITOR] WARN: Monitor #6 'Gitea': Pending: maxContentLength size of -1 exceeded | Max retries: 10 | Retry: 10 | Retry Interval: 60 seconds | Type: http
2022-10-20T13:25:36.657Z [MONITOR] WARN: Monitor #7 'web': Pending: maxContentLength size of -1 exceeded | Max retries: 10 | Retry: 1 | Retry Interval: 60 seconds | Type: http
2022-10-20T13:26:59.201Z [MONITOR] WARN: Monitor #6 'Gitea': Failing: maxContentLength size of -1 exceeded | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 20
docker-compose.yml
version: '3'
services:
uptime-kuma:
image: louislam/uptime-kuma:latest
container_name: uptime-kuma
volumes:
- /home//uptime-kuma/data:/app/data
- /var/run/docker.sock:/var/run/docker.sock
ports:
- 3001:3001
restart: always
Docker info:
Client: Docker Engine - Community
Version: 20.10.20
API version: 1.41
Go version: go1.18.7
Git commit: 9fdeb9c
Built: Tue Oct 18 18:20:18 2022
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.20
API version: 1.41 (minimum version 1.12)
Go version: go1.18.7
Git commit: 03df974
Built: Tue Oct 18 18:18:08 2022
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.8
GitCommit: 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
runc:
Version: 1.1.4
GitCommit: v1.1.4-0-g5fd4c4d
docker-init:
Version: 0.19.0
GitCommit: de40ad0
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 22 (8 by maintainers)
After some research, I managed to fix the issue, but I don’t exactly know what is happening here.
The solution is adding a header
Accept-Encoding: gzip, deflatehttps://stackoverflow.com/a/55918781/1097815
My guess is the plugin WP Fastest Cache do not handle plain text response without gzip correctly sometimes, force to gzip response fix the issue.
In curl, adding
--compressalso fix the issuecurl --compress https://www.estiafilosofia.org/Free feel to try
louislam/uptime-time:nightlyCurrently monitoring 99 properties, I’m having the same issue since yesterday, every ~15m from one website only.
I installed 2 days ago, I already have 1.19
Managed to replicate on demo, before it reset. You can try with https://www.estiafilosofia.org Just add a monitor and wait a few minutes. It does the MaxContentExceeded error and then goes back to OK randomly.
Still need a reproduce steps and try to reproduce in the demo site.
https://demo.uptime.kuma.pet