-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uptime-Kuma does not respond #4747
Comments
After a quick restart of the service, the monitors are back, but this is not very stable, is there any way to improve the stability of the Frontend ? |
Please see #3276 which this is a duplicate of or #4500 which tracks the resolution with this tip:
Tip If you are affected by the performance limits mentoned in the v2-tracking issue in The solution boils down to having a lower amount of data => making Uptime Kuma less worried about reading those gigabytes of data.:
|
(closing as a duplicate) |
🛡️ Security Policy
📝 Describe your problem
I have an instance of uptime-kuma added something like 100 monitors, the UI doesn't respond anymore, this is due to the volume of the monitors ?
Or this is normal ?
Also, another one is that the application is running and can send notifications when a monitor is down, the UI doesn't respond only.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.13
💻 Operating System and Arch
Helm Chart from Docker compose
🌐 Browser
I tried it from the latest firefox and from the latest chrome
🖥️ Deployment Environment
The text was updated successfully, but these errors were encountered: