Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

WebSocket connection to debugger failed

See original GitHub issue

Hi, I’ve sudenly started getting this strange error when trying to start debugger in Chrome. This is the full message: WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: One or more reserved bits are on: reserved1 = 0, reserved2 = 1, reserved3 = 1 The status on debugger page also changes to this: Status: Disconnected from proxy. Attempting reconnection. Is node server running?

Everything worked fine until today. I’ve even tried to clear all node module and reinstall them, while updating React Native version to the latest. I’ve also tried running packager with parameter --reset-cache. None of these helped.

Edit: I should add that I’m running Windows 10.

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:9 (5 by maintainers)

Top GitHub Comments

3reactions

yuyicommented, May 6, 2016

After I have uninstalled the ESET Smart Security, it looks like the problem is fixed. :p

1reaction

damusnetcommented, May 5, 2016

Seems close enough to me, and with > 500 issues, it feels right to try and group them whenever possible.

Top Results From Across the Web

WebSocket connection to 'ws://localhost:8081/debugger-proxy ...

Seem to have started getting this random error when debugging with chrome, it will debug for a while and then die with the...

How to debug websocket connection error with "Unknown ...

Update 1: I think you could reproduce it by closing the connection for a long time (I don't know the exact time) from...

Debugging WebSockets - Baeldung

Here, we open a WebSocket using SockJS and then subscribe to the topic /topic/ticks. Eventually, the client consumes and displays the messages ...

Troubleshooting - SAFE Documentation - SAFE Stack

You may see the following SocketProtocolError message in the Debug Console once you have started your SAFE application. WebSocket connection to 'ws://localhost: ...

Debugging using Chrome: Websocket connection failu... - Neo4j

html file of my web app, but when the app runs a Cypher query against the db, a Websocket connection failure results. Uncaught...