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.

Can't connect to server ?

See original GitHub issue

client error

WebSocket connection to 'ws://10.150.140.68:3888/socket.io/?EIO=2&transport=websocket' failed: Connection closed before receiving a handshake response socket.io-1.0.0-pre5.js:2
Resource interpreted as Image but transferred with MIME type text/html: "http://pingtcss.qq.com/pingd?dm=10.150.140.68:3887&pvi=8765514752&si=s63491…x768&scl=24-bit&lg=en-us&jv=1&tz=-8&ct=&ext=adid=&pf=&random=1401368717118". stats?sId=23713003:18
3
WebSocket connection to 'ws://10.150.140.68:3888/socket.io/?EIO=2&transport=websocket' failed: Connection closed before receiving a handshake response

client code


function connect (callback) {
  var socket = io("ws://10.150.140.68:3888", {transports: ['websocket',]});
  socket.on('connect', callback)
}

server code

var app = express.createServer()
var io = require("socket.io").listen(3888, {origins: '*:*'})
io.server.removeListener('request', io.server.listeners('request')[0]);

io.sockets.on('connection', function(){
    console.log('connection');
})

server error


* started http://0.0.0.0:3887/
   warn  - unknown transport: "undefined"
   warn  - unknown transport: "undefined"
   warn  - unknown transport: "undefined"
   warn  - unknown transport: "undefined"
   warn  - unknown transport: "undefined"
   warn  - unknown transport: "undefined"
   warn  - unknown transport: "undefined"
   warn  - unknown transport: "undefined"
   warn  - unknown transport: "undefined"
   warn  - unknown transport: "undefined"
   warn  - unknown transport: "undefined"

Issue Analytics

State:
Created 9 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

2reactions

randylaymancommented, Jan 23, 2015

For anyone who comes across this via Google, this error message can be caused by having different versions of socket.io-client and socket.io. In my case client was version 1.3.6 and server was 0.9. Downgrading the client to 0.9 made the error go away and allowed me to connect successfully.

0reactions

punkagecommented, Oct 12, 2016

@randylayman Thanks!!!