Log storming in traefik while using Dockge

[lordraiden]

⚠️ Please verify that this bug has NOT been reported before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

When I'm in the screen above, I get hundreds of logs entries per second in traefik and I guess the same will happen in any other proxy related with this domain "socket.io"

100.100.100.21 - - [07/Jan/2025:21:26:29 +0000] "GET /socket.io/?EIO=4&transport=polling&t=PH2gNTm&sid=T4JG1BCsoWcvHPK9AAAM HTTP/2.0" 200 309 "-" "-" 11352 "dockge@docker" "http://10.10.40.41:5001" 0ms

With other stacks I get the same logs entries but not hundreds per second is this a normal behavior? should there be some kind of cool down? what is the purpose of that request?

then in dockge I get this logs but only for this stack, why this stack is special?

2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint

👟 Reproduction steps

See above

👀 Expected behavior

See above

😓 Actual Behavior

See above

Dockge Version

1.4.2

💻 Operating System and Arch

Unraid

🌐 Browser

Firefox

🐋 Docker Version

Client: Version: 24.0.9 Context: default Debug Mode: false Plugins: compose: Docker Compose (Docker Inc.) Version: v2.29.2 Path: /usr/local/lib/docker/cli-plugins/docker-compose

🟩 NodeJS Version

No response

📝 Relevant log output

2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:14Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:15Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:15Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint
2025-01-07T21:24:16Z [TERMINALRESIZE] INFO: Terminal: compose--webproxyint
2025-01-07T21:24:16Z [TERMINALRESIZE] INFO: Terminal: combined--webproxyint

[lordraiden]

Not sure but due to the log type it might be related to this
#533

[louislam]

This indicates that Dockge (or socket.io) cannot be connected via WebSocket, usually because Dockge is behind a reverse proxy without proper config to allow WebSocket.

Please check this:
https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy