Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

WebSocket connection to failed: Invalid frame header

See original GitHub issue

WebSocket connection to 'ws://10.1.30.58/socket.io/?EIO=3&transport=websocket' failed: Invalid frame header

server debug:

 socket.io:server incoming connection with id 7hnvZ1RkTsCgjyVVAAB- +4ms
 socket.io:client connecting to namespace / +3ms
 socket.io:namespace adding socket to nsp / +1ms
 socket.io:server incoming connection with id gOcFr2YHNcmSF9hqAAB_ +2ms
 socket.io:client connecting to namespace / +2ms
 socket.io:namespace adding socket to nsp / +1ms
 socket.io:namespace next called after client was closed - ignoring socket +74m

 socket.io:namespace next called after client was closed - ignoring socket +2ms

 socket.io:namespace next called after client was closed - ignoring socket +1ms

 socket.io:namespace next called after client was closed - ignoring socket +2ms

 socket.io:namespace next called after client was closed - ignoring socket +2ms

 socket.io:namespace next called after client was closed - ignoring socket +1ms

On client side: var socket = io({transports: ['websocket']}); //socket.io

What’s wrong?

Issue Analytics

State:
Created 7 years ago
Reactions:2
Comments:26

Top GitHub Comments

7reactions

mikecanncommented, Aug 11, 2021

For me the answer was that I was connecting with a client that was version 2 and the server was running version 4. As per the docs I had to enable allowEIO3 on the server

2reactions

carloverhammecommented, Oct 21, 2018

Same issue, I only get the error in the chrome console