Got "Lost connection to the socket server. Reconnecting..." everytime when I open kuma site, how can I check the log?

[baalchina]

⚠️ Please verify that this question has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

Hi, I installed kuma by docker in a rocky 9.3 linux, with this command:
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1

But everytime when I tried open site(without login), I got a "Lost connection to the socket server. Reconnecting..." error, after some time (maybe 1 or 2 min), the error disappare, everythings seems fine.

I tried using a reserve proxy(with config in here https://github.com/louislam/uptime-kuma?tab=readme-ov-file#advanced-installation ), or direct visite the ip:3001, still got the same error.

So, how can I check the error log?

Add:
I newly installed a fresh Rocky 9.3 server, with docker 25.0.1, and new uptime-kuma , visit using ip:3001, still got lost conneciton. And the docker logs shows the same like below.

📝 Error Message(s) or Log

(docker logs, seems no error?)

🐻 Uptime-Kuma Version

1.23.11

💻 Operating System and Arch

Rocky 9.3, docker

🌐 Browser

Chrome,edge,firefox

🐋 Docker Version

20.10.13

🟩 NodeJS Version

No response

[CommanderStorm]

So, how can I check the error log?

sudo docker logs uptime-kuma


I think a file you tried to attach was not fully done uploading..

[baalchina]

So, how can I check the error log?

sudo docker logs uptime-kuma


I think a file you tried to attach was not fully done uploading..

sorry, i update the attach in the origin post..

[chakflying]

I think this is more of a front-end issue, would be great if you also take a look if there are any browser console errors (but I think it's unlikely).

I also noticed that the polling connection method seems to behave a bit weird compared to before, but further investigation would require deeper knowledge of how socket.io works first.

[baalchina]

I think this is more of a front-end issue, would be great if you also take a look if there are any browser console errors (but I think it's unlikely).

I also noticed that the polling connection method seems to behave a bit weird compared to before, but further investigation would require deeper knowledge of how socket.io works first.

This is the chrome console error. In this picture I got 2 error then seems connected, and kuma works fine. In some other times will be more and more same error...

[chakflying]

400 seems connected to #4409.

[CommanderStorm]

continuing to debug this in #4409 as I think they are the same issue.
If during said process we discover that this is a different issue, we will reopen
=> closing as duplicate