Node.js with Socket.io - Long Polling fails and throws “code”:1,“message”:“Session ID unknown” response

Question

I\'m stuck on why a node.js app that was moved to an IIS7 server is now failing. I know IIS7 doesn\'t support web sockets but my understanding was that socket.io would fall

Answer 1

Had the same error recently with socket.io: {"code":1,"message":"Session ID unknown"} for web sockets connection, though setup is different (nginx + passenger + nodejs). The issue was broken connection from NodeJS to Redis which I have in my NodeJS app. So once Redis was properly started (it was an IP binding issue), socket.io started to communicate properly via web sockets. If you're stuck on the same problem, check that your NodeJs app is working properly (e.g. it connects to all required resources)

Answer 2

In my project, I tried adding the transport option as a websocket and error no longer appears.

io.connect(url, {
   "transports": ['websocket']
})

It will be a problem with supporting IE and other old browsers as they don't support native websockets, if the application browser compatibility is not an issue this seems a solution.

Answer 3

for me, it was with nginx ssl http2, and it was polling, so the good config is:

 const ioSocket = io('', {
      // Send auth token on connection, you will need to DI the Auth service above
      // 'query': 'token=' + Auth.getToken()
      path: '/socket.io',
      transports: ['websocket'],
      secure: true,
    });

Answer 4

If you use Socket.io-Redis then it looks like a situation described in bug tracker of Socket.io:

https://github.com/socketio/socket.io/issues/1739#issuecomment-64244359

Answer 5

For socket.io v2.0.3 (js client),when you use socket.io on client side the client socket.io makes some network calls as explained:

1. When io.connect() is called, the socket.io library makes a call to the server which looks like

   ?EIO=3&transport=polling&t=LqtOnHh,

   server responds with something like

   "90:0{"sid":"pcJM_AEZirrJT-DuAAUy","upgrades[], "pingInterval":3600000,"pingTimeout":3600000}2:40"

   here the server generates a socket object on server side and sends its id back to the client.

2. After this client makes another call to the server which is something like

   ?EIO=3&transport=polling&t=LqtR6Rn&sid=0JFGcEFNdrS-XBZeAAXM

   this is the long poll call that client makes to the server, if you see here it is passing the sessionId which it received in first call above, if the call goes to same node which generated that sessionId, the node identifies the socket connection for which the request has been made and responds.

   But behind ELB the call may go to some other node that didn't generate this sessioId, in that case the node will not be able to identify the sessionId for which the call was made and hence responds with {"code":1,"message":"Session ID unknown"}

You will also see this error in case of long polling not getting answered or getting timeout.