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
Still getting Continual Transport Close every PingInterval | Redis Adapter #4333
Comments
Sorry @darrachequesne i am reposting this one #4298 to better describe the situation. We can close it and continue discussion here if it helps! |
Also have the client HAR and server logs if it helps |
@aaronkchsu Could it be possible that some of the client still have a Socket.IO v2 client? That would explain the disconnection on the first ping (the client send a PING packet after 25000 seconds, but the server is supposed to send PING and receive PONG in v3/v4). |
I have a similar problem with a flask-socketio server app hosted behind an aws alb and the client socket session seems to be consistently disconnecting every 26 seconds. Traceback (most recent call last): Client requests use /socket.io/?EIO=3&transport=polling&t=O9hzOSn&sid=xxxx Server version of SocketIO is 4.6.0 |
Closed in favor of #4298. |
Describe the bug
A clear and concise description of what the bug is.
I know there is another thread on this #3025, but I read through and tried everything and still can't fix this problem, I have loved this package so far but can't seem to get this right!
I have a lot of clients connecting around 7k cc okay but I get a few clients reporting they are having disconnect issues. Looking deeper it shows that on the server they are reconnecting and disconnecting every 25 seconds (see logs below)
My pingInterval is 25000
My pingTimeout is 65000
"@socket.io/redis-adapter": "^7.1.0",
"socket.io": "4.4.1",
I'm using Amazon's ALB to 4 targets with redis adapter with a 1-minute timeout and sticky session enabled 100 seconds
Server Code
Client code (disabled polling and enabled both didn't work)
Bugged behavior server logs, you can see it's getting a transport close every 25000
The text was updated successfully, but these errors were encountered: