Community

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

socket.io

Technical Support

1 Posts 1 Posters 353 Views

M Offline

M Offline
midnightbeast
wrote on last edited by

#1

I tried running nodebb on apache but given I was running under a centos/whm server, it became a nightmare. Now i have nodebb running on Digitalocean but I still get this error like

https://coinassist.org/socket.io/?EIO=3&transport=polling&t=MBL7iKu

Is that normal?
1 Reply Last reply
0

Suggested Topics

G

Socket.io connection error, ipv6 address

Scheduled Pinned Locked Moved Technical Support

0 Votes

2 Posts

300 Views

G

SOLVED

Added
socket.io {"address": */*};
Default "address:" **; that's is problem.
G

Delaying sockets start

Scheduled Pinned Locked Moved Technical Support

0 Votes

6 Posts

340 Views

G

It looks like is a configuration problem. When I load the page, there is this network error:

socket.io.js:8 WebSocket connection to 'wss://example.com/socket.io/?EIO=3&transport=websocket&sid=zV8kYkx-87ULGIjGAAAF' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR

On Chrome's inspector window it says it was canceled.
But then it works normal.
So all I need is to bypass the first error... or even better, fix it.
J

warn: Flooding detected! .... warn: [socket.io] Too many emits!

Scheduled Pinned Locked Moved Technical Support

0 Votes

4 Posts

337 Views

J

Sorry, I didn't really process your full message. At the end you state your guess these are users with connection problems who got reconnected... based on the relatively small number of times I see this warning, as compared to over-all traffic to the forum, it sounds like I can probably ignore the warning. Thanks for your help.
J

nodebb on aws is throwing sockets error

Scheduled Pinned Locked Moved Technical Support

0 Votes

10 Posts

1137 Views

S

We got ours fixed, ignore me 🙂

Nothing to do with AWS, someone had changed our nGinx config and not told me.
A

socket.io Bad Gateway - fix?

Scheduled Pinned Locked Moved Technical Support nginx socket.io 502 bad gateway cloudflare

0 Votes

7 Posts

4068 Views

S

Try removing the SPDY support and see if it works. I had to disable SPDY with SSL to get it to towork.

Community

socket.io

Suggested Topics

Socket.io connection error, ipv6 address

Delaying sockets start

warn: Flooding detected! .... warn: [socket.io] Too many emits!

nodebb on aws is throwing sockets error

socket.io Bad Gateway - fix?