mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Error: "Lost connection to the socket server" | It happens on adding a large json file! #1386
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#1386
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @perpi on GitHub (Sep 10, 2022).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
Description
No response
👟 Reproduction steps
Try to add more than 500 items by one json file.
👀 Expected behavior
Adding json files with any size.
😓 Actual Behavior
By importing more than 400 addresses (>50,000 lines in JSON file), Kuma couldn't add them showing this error:
🐻 Uptime-Kuma Version
1.18.0
💻 Operating System and Arch
Ubuntu 22.04 64bit
🌐 Browser
Chrome, Edge, Firefox
🐋 Docker Version
Docker version 20.10.12, build 20.10.12-0ubuntu4
🟩 NodeJS Version
v16.16.0
📝 Relevant log output
No response
@wojcikm commented on GitHub (Sep 22, 2022):
@louislam any ETA on this?
@arioch commented on GitHub (Nov 14, 2022):
First time user, already ran into this error with a mere 10 items.
What's the current preferred way to bulk import? The usual self-help channels lead me to the JSON import approach.
@jstewart1982 commented on GitHub (Nov 21, 2022):
We are encountering this issue now, we have just over 1000 sensors and the console seems to be rendered inoperable
@jkrause-Gold commented on GitHub (Feb 16, 2023):
Same issue here. Dashboard just keeps cycling through all the endpoints then errors out. "Lost connection to Server Socket Reconnecting......"
Dashboard is almost useless at this point
@johnny-chiang commented on GitHub (Feb 21, 2023):
Had the same issue here
@PatyYe commented on GitHub (Apr 21, 2023):
We have 3 instances, 2 of them both with ~300 monitors. These respond without issue but tend to be a bit slow starting up. Our third instance is at 1100 monitors, and we broke down around 800, it keeps loadin and loading.
I cannot use the dashbaord anymore.
If wanted I can provide additional information if it's required to help find the issue.
@nocerainfosec commented on GitHub (Apr 26, 2023):
I am able to add 600 sensors per json file, I have added 1186 sensors to monitor in total, although, server becomes unresponsive after every 2 minutes losing connection with these 1186 sensors. is there anything that can be done to increase performance?
@goksinenki commented on GitHub (Oct 19, 2023):
I have nearly 600 sensors and same problem. There is nginx proxy before Kuma and configured as told in the articles.
server {
listen 8000;
# Remove '#' in the next line to enable IPv6
# listen [::]:80;
server_name xxxx.xxxxx.local;
location / {
proxy_pass http://localhost:3001;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
}
}
And the nginx log says : "[error] 67395#0: *226 recv() failed (104: Connection reset by peer) while proxying upgraded connection, client: 10.x.y.z, server: xxxx.xxx.local, request: "GET /socket.io/?EIO=4&transport=websocket HTTP/1.1", upstream: "http://127.0.0.1:3001/socket.io/?EIO=4&transport=websocket", host: "uptime.xxxx.xxx:8000"
Any Updates ?
@CommanderStorm commented on GitHub (Oct 19, 2023):
v2 does include a lot of perfomance updates and should allow scaling past ~200-500 monitors.
See https://github.com/louislam/uptime-kuma/milestone/24 for further progress
@xyhcode commented on GitHub (Dec 8, 2023):
I didn't add any monitors, but the actions panel is always like this, refreshes every few seconds, so why
@chakflying commented on GitHub (Dec 9, 2023):
Obsolete as the backup feature has been dropped in https://github.com/louislam/uptime-kuma/pull/3892.
@hrshv6 commented on GitHub (Apr 2, 2024):
In our case, the cause of this error was haproxy. To solve this problem, we needed to add the following two settings to our haproxy.cfg file:
Just wanted to comment in here for other people looking for a solution.
@CommanderStorm commented on GitHub (Apr 2, 2024):
@hrshv6
Completely unrelated to the other posts. NONE of them have stated that they are using haproxy.
This post is about connection timeouts caused by the now removed import/export functionality and thus between db and backend