Socket.io not working

[abacaj]

Socket.io not working

[RafalWilinski]

Might be silly but refresh the page and everything will be alright :D

Of course I'll try to fix that asap.

[afollestad]

I'm getting the same error pretty frequently, it's on an HTTPS server btw

WebSocket connection to 'wss://[url-here]/socket.io/?EIO=3&transport=websocket&sid=gt_zkj220dRXa8SDAAAD' failed: Connection closed before receiving a handshake response

[AussieFlem]

That's a very similar error what I'm seeing in #27 (FWIW)

[jabis]

@afollestad are you using a real cert, or self-signed one? At least some node versions will cease to co-operate without a valid one. You can - but shouldn't - use certain env-vars in your app (on the top of my hat process.env['NODE_TLS_REJECT_UNAUTHORIZED'] = '0';, should do it for self-signed certificates, which I usually use on development environments ( so btdt in another context; )

[afollestad]

@jabis a real cert, on a remote server

[jabis]

@RafalWilinski I believe this are two distinct errors, as the OP is having 404 not found, while @afollestad is having a handshake error, would be wise to split maybe.
@afollestad next I'd like to point out that if you're not reverse proxying the /socket.io yours could very well be cross-origin problem. Are you just deploying the example as it is, or are you trying to integrate it with some other existing software (maybe using another socket.io already)?

[afollestad]

I'm not doing anything special; it should work as is.

[jabis]

@afollestad if you access www.remote.tld and you access the serverside component from www.remote.tld:4000 then that is considered cross-origin, at least on modern chrome and firefox browsers :) If you on the other hand are reverse proxying the /socket.io port to "upstream" aka node process, then it should not be, and depending on your httpd, and node version, could be a proxy option or header problem - https( read: wss for sockets ) is really touchy with cross-origin, scripting.