WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: Invalid frame header

[cgreening]

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

WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: Invalid frame header

We're using version 0.22 on the Mac with iOS

[gwhite-dayspring]

Also having this issue

[tal952]

+1
I restart my computer, and its gone.

[robclouth]

Same. Version 0.22 on Mac with iOS.

[HeWasntOffByMuch]

so has this been fixed? I'm running http server in node, listening on port 3001 and after react-native recieves any error (like parse Error for example) I need to restart it and react-android app no longer connects to that node server. I end up with just that message in debugger:
"WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED"
I set up adb connection over wifi, 'adb devices' shows my phone and app starts normally - but doesnt connect over 3001

EDIT:
react-native-cli: 0.2.0
react-native 0.24.1

[rupeshdeotale97]

Also having same issue

[alexandrunicolae]

try running 'adb reverse tcp:8081 tcp:8081' in terminal to access the development server from the device

[bitfused]

Same issue here on 0.24 version for iOS

[ws2356]

same issue, react native 0.26.3

[ultragtx]

I have the same issue when using Chrome, but it won't happen if I use https://github.com/jhen0409/react-native-debugger.

[millerm]

Experiencing the same issue with react-native: 0.28.0

EDIT: found a fix - https://medium.com/@davidguandev/lets-build-a-react-native-application-4190839a4f5c#.2jswlrano

[Exilz]

@millerm are you referring to the ATS configuration in xcode ?

If so, it doesn't solve it for me. OSX / React native 0.28

Edit: --> I found a quick workarround that works for now by opening chrome in incognito mode

[hendrikswan]

Perhaps it's antivirus? #7413

[KGALLET]

Have the same issue

RN 0.28
MAC OS

[hendrikswan]

A colleague of mine had the same issue on node version 6.x. He downgraded to the same version I'm running, v5.9.1, and it resolved his issue.

[Exilz]

Yup, I can confirm that Node 6.3 was the problem for me.

I downgraded as @hendrikswan suggested, but to version 6.2 and everything has been running without problems for a few hours.

[phil-travelbytes]

Downgrading of Node from 6.3.0 to 6.2.2 didn't work for me;
Issue still persists.

[hendrikswan]

Maybe downgrade further?

On Fri, 15 Jul 2016 at 08:47 Phillip Kingston [email protected]
wrote:

Downgrading of Node from 6.3.0 to 6.2.2 didn't work for me;
Issue still persists.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#6627 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQsNZ1PwiqFnsXzGdPXWjsgYg-pg-w9ks5qVyz-gaJpZM4H4D2Z
.

[ide]

I think this might be "fixed" in RN 0.30 which uses ws 1.1.1, which doesn't try to install native helper modules by default and should work more consistently across V8 versions.

[julienvincent]

Can someone confirm if RN 0.30 fixes this?

[ts-ign0re]

Have the same thing

[julienvincent]

I can confirm it is greatly improved in RN30. The error still pops up occasionally but its rare enough for it not to be a hindrance anymore.

[stewart42]

RN 0.30.0 does appear to be much better, not getting the error on node 6.3.1. I was getting it with RN 0.29.0

[chrisfisher]

Upgrading from 0.29.0 to 0.30.0 also seems to have fixed the issue for me.

[waleedarshad-vf]

same error with RN 0.27.2

[ide]

Closing this issue since it's only happening with old versions AFAIK. Please open a new issue if the problem described in the first post is happening with RN 0.33+.

[MarkPare]

Similar error is preventing me from using Chrome dev tools for debugging React Native app.

WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

node v7.2.1
react-native-cli: 1.2.0
react-native: 0.44.0

[psoulages]

Hello MarkPare,

I am having the same issue, inside react-native debugger console error follows: WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

My Terminal is red and reads 'No Bundle URL Present'. Weird enough, my others aps I have made in the same folder don't have this issue.

react": "16.0.0-alpha.6",
"react-native": "^0.42.3",
"react-native-router-flux": "^3.39.1",
"react-redux": "^5.0.5"

Has anyone come across this recently?

[psoulages]

@MarkPare ^ :)

[ghost]

Getting this on RN 0.45.1 :(

[salilbajaj]

Same Issue RN 0.45.1

[LAITONEN]

Same issue RN 0.47

[BarthesSimpson]

Me too

[Prateek479]

+1 same error in debugger , getting hard day by day to use RN :(

[Joeyrodrigues92]

Same issues

"react": "16.0.0-beta.5",
"react-native": "0.49.3",
"react-redux": "^5.0.6",

[anerivala]

Having the same issue...

[Bulinator]

+1 => WebSocket connection to 'ws://localhost:19000/debugger-proxy?role=debugger&name=Chrome' failed: Connection closed before receiving a handshake response

[erwinwahyura]

Having the same issue...

"react": "16.0.0",
"react-native": "0.51.0",

[IvanIvaschenko]

having same issue.
"react": "^16.2.0",
"react-native": "^0.52.0".
Mac OS.

[deno028]

having same issue after update to:
"react": "^16.2.0",
"react-native": "0.52.1"
running android emulator
MacOS

[WojciechCendrzak]

having the same issue:
"react": "^16.3.0-alpha.1",
"react-native": "0.54.1",
iOS

[lucidtheory]

When this happened to me I had the computer simulator and the device running at the same time. So it might have something to do with conflicting simulators

[sarneetk]

What fixed the issue for me => cleared my local cache using yarn clear cache then did a yarn install and ran the app again.

[leoabacade]

same issue
"react": "16.3.1",
"react-native": "0.55.4",

[tapumandal]

If you are using pusher server use cluster. I think error will be gone.

[PLopezD]

Any solution?

[aswinehart]

Having the same issue with RN 0.54.0