3

Can anyone help me with this weird error that I'm facing since last week which is specific to windows 10 home edition (all browsers). Its weird, as this error has arisen in a system which has been working fine since last 3 years (incl win 10 pc home/prof).

Error - "failed: One or more reserved bits are on: reserved1 = 0, reserved2 = 1, reserved3 = 0 " [ hence cannot connect to server ] ... however this works fine in a Windows 10 professional PC

Socket.IO Version - 0.9.16 ( wss://127.0.0.1:3000 ) ... behind NGINX with self-signed certificates OS - Windows 10 Home Edition Browser - Latest Chrome/Firefox Node - v0.10.31

chiragajmera
  • 58
  • 1
  • 5
  • 1
    Hey, Im sorry I copied your text to create an issue on socketio github. I hope someone could give us some insight on this problem https://github.com/socketio/socket.io/issues/2543 – Tomás May 09 '16 at 17:39

1 Answers1

1

TL;DR

  1. Update nginx.
  2. Uninstall ESET NOD32 antivirus

1) Nginx:

See this if it helps:

WebSocket connection failed: One or more reserved bits are on: reserved1 = 0, reserved2 = 1, reserved3 = 1

Found the answer at the bottom of an Nginx blogpost: I needed to upgrade my Nginx version to a 1.3.13+. Installed the 1.10 (latest stable) using the right Nginx Debian repository (see instructions), and it seems to works fine now :)

2) ESET NOD32

Last week they updated their software putting more restriction on websockets connections.

Here is the eset nod32 thread which explains the problem:
https://forum.eset.com/topic/8355-protocol-filtering-breaks-websockets-after-update-at-5052016/ Refer to this github thread for more information about it: https://github.com/socketio/socket.io/issues/2543#issuecomment-218010922

Community
  • 1
  • 1
Tomás
  • 3,501
  • 3
  • 21
  • 38