Some Chrome browsers not connecting


#1

I have some clients on Chrome that are not connecting. Our debug log looks like this:

09:49:28: log: WARNING: connect error, id: undefined , error: websocket error
09:49:28: log: WARNING: WebSocket closed, code: 1006
09:49:28: log: WARNING: connect error, id: undefined , error: websocket error
09:49:28: log: WARNING: WebSocket closed, code: 1006
09:49:28: log: DEBUG: reconnect attempt, id: undefined , attempet: 1
09:49:28: log: DEBUG: reconnecting, id: undefined , attempet: 1
09:49:28: log: WARNING: connect error, id: undefined , error: websocket error
09:49:28: log: DEBUG: error reconnecting, id: undefined , error: websocket error
09:49:29: log: DEBUG: reconnect attempt, id: undefined , attempet: 1
09:49:29: log: DEBUG: reconnecting, id: undefined , attempet: 1
09:49:29: log: WARNING: connect error, id: undefined , error: websocket error
09:49:29: log: DEBUG: error reconnecting, id: undefined , error: websocket error
09:49:30: log: DEBUG: reconnect attempt, id: undefined , attempet: 2
09:49:30: log: DEBUG: reconnecting, id: undefined , attempet: 2
09:49:30: log: WARNING: connect error, id: undefined , error: websocket error
09:49:30: log: DEBUG: error reconnecting, id: undefined , error: websocket error
09:49:30: log: DEBUG: reconnect attempt, id: undefined , attempet: 2
09:49:30: log: DEBUG: reconnecting, id: undefined , attempet: 2
09:49:30: log: WARNING: connect error, id: undefined , error: websocket error
09:49:30: log: DEBUG: error reconnecting, id: undefined , error: websocket error
09:49:34: log: DEBUG: reconnect attempt, id: undefined , attempet: 3
09:49:34: log: DEBUG: reconnecting, id: undefined , attempet: 3
09:49:34: log: WARNING: connect error, id: undefined , error: websocket error
09:49:34: log: WARNING: reconnect failed, id: undefined
09:49:34: log: DEBUG: Event: disconnect
09:49:34: log: INFO: Socket disconnected, lost connection to ErizoController
09:49:34: log: ERROR: Unexpected disconnection from ErizoController
09:49:34: log: DEBUG: Event: room-disconnected
09:49:34: log: DEBUG: error reconnecting, id: undefined , error: websocket error
09:49:35: log: DEBUG: reconnect attempt, id: undefined , attempet: 3
09:49:35: log: DEBUG: reconnecting, id: undefined , attempet: 3
09:49:35: log: WARNING: connect error, id: undefined , error: websocket error
09:49:35: log: WARNING: reconnect failed, id: undefined
09:49:35: log: DEBUG: Event: disconnect
09:49:35: log: INFO: Socket disconnected, lost connection to ErizoController
09:49:35: log: ERROR: Unexpected disconnection from ErizoController
09:49:35: log: DEBUG: Event: room-disconnected
09:49:35: error: mediaRoom disconnected, event Type: [object Object]
09:49:35: log: DEBUG: error reconnecting, id: undefined , error: websocket

I can’t find anything different between those that connect and those that don’t. Those that can’t connect can never connect. Firefox for those users however works ok.

Where does the erizo client get its copy of socket.io? The one that I am loading from the for my app or from the erizo server?

Marlin


#2

currently erizo loads it’s own socket.io from licode/erizo_controller/erizoClient/lib/socket.io.js

It maybe could be that your firewall is blocking the ws transport on some of these clients or they have some type of extension in chrome that blocks the websocket traffic.

This is a POC but you can try to merge my modifications to allow users to use polling as a fallback if websockets doesn’t work.
This was disabled to allow implementing the “reconnect” feature.
It’s a quite ugly implementation but you can try to get it a shot

Remember to recompile the client!


#3

I have made those changes but I can’t get someone to test yet I will let you know. Everyone switched to FireFox which does not have the issue.