-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
page error message“Lost connection to the socket server. Reconnecting...” #4409
Comments
|
|
Given that the error message is stating that the |
just a guess (comparing #4422 and my working setup): |
Okay, so it is not the runtime, nor the docker version. I have never worked with said OS. Are there any firewalls on said OS that might be active? |
Well, i disabled firewalld in my rocky linux, and tried to open uptime-kuma in a single pc but three browsers(firefox, edge, chrome), only firefox display the lost connection to the socket server, but soon became normal. I'll try again later. |
Can you reproduce the issue on our demo site? |
|
Weird. I cannot reproduce. 2 possible directions:
|
Let's find commonalities. @louislam what brower are you running? |
Tried several combinations and tried several times. Also Chrome 121.0.6167.85, maybe I missed some important steps to reproduce. Test 1:
Test 2 (From vue router):
|
I have tried multiple times again and cannot reproduce what I could reproduce before. This bug be like: Going back to basics (i.e. the docs): https://socket.io/docs/v3/troubleshooting-connection-issues/#in-the-network-monitor-of-your-browser
@macaty might there be a second server somewhere or might there be something caching responses or might there be something tampering with the traffic we send out? |
Have not look into it yet, but it seems that it is an upstream bug. As it is also reported recently and op doesn't seem to be using multiple nodes. If it is true, maybe we should rollback to the previous working version. |
docker ps|grep uptime docker version Server: |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Suddenly the same error occurs in the GUI: Connection to socket server lost. Restoring the connection...
The setup is done with docker compose. It has been running successfully for many months. Around 50 monitors. Docker log:
And it goes on like this. We have reduced the monitor history to 1 day and emptied the database (it was about 1 GB in size) without anything changing. All browsers show the same behavior. We are now somewhat at a loss. Does anyone have any ideas? |
Oddly, I'm also getting the same issue. I'm not sure when this happened as I don't usually visit the dashboard - unless a service goes down. Navigating to the IP directly (e.g. http://192.168.1.123:3001/) gives no issues. Using a reverse proxy (I'm using traefik) and navigating to something like https://uptime.mydomain.com, results in the behavior that @kingfisher77 described. |
Yes, missed to mention this. We are behind traefik too. |
Looks like you guys are affected by this? #4669 |
Thank you! It looks like that was the issue. |
Fantastic! Thank you. |
🛡️ Security Policy
Description
When click on or jump to manage-status-page 【 http://x.x.x.x:6001/manage-status-page】 from status pages【http://x.x.x.x:6001/status/monitor】 ,we got an error message ,like "Lost connection to the socket server. Reconnecting..."
The detailed error message is as follows, please help:
error url: http://x.x.x.x:6001/socket.io/?EIO=4&transport=polling&t=OqqPZ0i&sid=bdBgD95f9Dm-G10IAAGH
404 status respone:{"code":1,"message":"Session ID unknown"}
👟 Reproduction steps
refer to Description
👀 Expected behavior
refer to Description
😓 Actual Behavior
refer to Description
🐻 Uptime-Kuma Version
louislam/uptime-kuma:1.23.11
💻 Operating System and Arch
centos 7.9
🌐 Browser
chrome 120.0.6099.225
🐋 Docker Version
No response
🟩 NodeJS Version
No response
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered: