Websockets causing 400 error on hosted servers

A few updates ago, sockets stopped working on my hosted server, I assumed this was due to a server issue and just continued development on localhost, but I’ve now switched to another server where the same issue occurs.

With debugging enabled, any server connect with sockets enabled results in the following. There are also no errors in the console:


No particular errors under response tab. Tried on two servers, running two separate OS’s, in separate DC’s.

However, the sockets work completely fine on http://localhost:3000/ and everything loads as expected there. Has anyone else been experiencing this, or knows a fix?

Community Page
Last updated: