Ratchet: WebSocket connection to 'ws://localhost:1337/' failed: One or more reserved bits are on: reserved1 = 0, reserved2 = 1, reserved3 = 1

[consigliere23]

What about this?
Everything worked and it suddenly appeared as error?

[henryoswald]

Are you on windows?

[cboden]

That is a protocol error. It most likely means the client attempting to connect did something it wasn't supposed to be doing.

[consigliere23]

Yes I am on Windows. The problem is in Chrome and FF. But on the another win 7 laptop sockets are working normaly. What is the issue here and is there anything to do in order to solve? I also tried with disabling antivirus but it did not help.

@cboden who is doing that and what is not supposed to be done?

[henryoswald]

I am not involved in Ratchet at all but we have started seeing some websocket issues on windows in the past couple of days. We use Socket.io on node so very different tech stack.

[consigliere23]

Ok, but how did you fix this issue? Is this some general problem with windows or maybe with latests updates in chrome and FF?

[consigliere23]

Can anyone assists me with this? I am using Autobahn|JS, on android everything is working as it should be. What can be the cause? I do not know is the problem on back-end of php ratchet or in JS or maybe something else? I am using push integration.

[mwsv]

I'm facing exactly the same problem using Ratchet/Autobahn.js through the gos/web-socket-bundle, I tested my project on more than 10 workstations with Windows and the problem occured on three of them, in all of main browsers (Opera, Chrome, FF, IE) in these cases. I don't see the problem on Ubuntu machines too. It's really hard to guess how to fix it, so thanks for any help to resolve this weird issue.

[dmitriyGarden]

This error is also in official demo page. https://monosnap.com/file/GDN0cLOVTjT0EJVDNlBOyP8dPTpk6E

[consigliere23]

This URL is broken :(

[dmitriyGarden]

Sorry. New screenshot http://take.ms/LaKmJ

[consigliere23]

I can see now thanks, but as I can see there is still no patch for this :(

[dmitriyGarden]

I'm have issues with WebSocket last days too. And try find resolve

[dmitriyGarden]

Another site, another tech, but similar problem http://take.ms/QOVFl

[dmitriyGarden]

I have idea. I seen trouble with protocol ws:// but protocol wss:// work correct. For example http://websocketstest.com/

[mwsv]

I have the same problem with wss:// protocol too.

[jeremy-saidani]

Hi guys !
Same problem for me, but I just find something :
https://forum.eset.com/topic/8355-protocol-filtering-breaks-websockets-after-update-at-5052016/
Works for me !

Find here : http://stackoverflow.com/questions/37117080/socket-io-has-stopped-working-since-last-1-week

[consigliere23]

So, all this is due to ESET NOD32 Antivirus recent update?

[jeremy-saidani]

If NOD32 is installing on your computer yes. It's works for me.
Is it working for you ?

[consigliere23]

Yes, I have NOD32.
I added IP addresses in exclude list and it works.

[jeremy-saidani]

I did the same !
Hope the next update of NOD32 will fixe this ...

[dmitriyGarden]

I resolved the trouble with WebSockets. Use wss:// instead ws:// and proxy through nginx ssl.
Users will not be waiting for update antivirus. My application must work.

[sudoanand]

Hi, recently I ran into the same issue in a custom socket server that I wrote in PHP.

I was masking the data to be broadcasted wrong.
The PHP terminal output is where you wanna look if you are doing something similar.