You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using Socket.io version 16.1.1, and normally, it works fine with AWS Load Balancer with only 1 node.
My team then tried to up the spec to 2 nodes, and now the iOS side is experiencing an endless connect-disconnect loop, as if the connection won't stick. (note: URL is wss)
Below is the socket config: socketManager = SocketManager(socketURL: url, config: [ .log(true), .connectParams(params), .path("/caregiver-ws/"), .reconnects(true), .forceNew(true) ])
*i tried with forceWebsocket(true), but the weird part is, with forceWebsocket(true), the socket would not even connect, and is in a loop of reconnection
**the android client works fine, so I'm stuck
Any respond or help would be appreciated, thank you!
The text was updated successfully, but these errors were encountered:
Hi, it was resolved on my end by hitting up my team that is responsible for the AWS setup. We used ALB and NLB at first, and ended up only using ALB only. Then, we set up stickiness for the ALB, and it solved my issue when scaling up to multiple nodes.
The socket manager setup is unchanged on my end.
Hopefully this helps.
I've been using Socket.io version 16.1.1, and normally, it works fine with AWS Load Balancer with only 1 node.
My team then tried to up the spec to 2 nodes, and now the iOS side is experiencing an endless connect-disconnect loop, as if the connection won't stick. (note: URL is wss)
Below is the socket config:
socketManager = SocketManager(socketURL: url, config: [ .log(true), .connectParams(params), .path("/caregiver-ws/"), .reconnects(true), .forceNew(true) ])
*i tried with forceWebsocket(true), but the weird part is, with forceWebsocket(true), the socket would not even connect, and is in a loop of reconnection
**the android client works fine, so I'm stuck
Any respond or help would be appreciated, thank you!
The text was updated successfully, but these errors were encountered: