X
Tap here to go to the mobile version of the site.

منتدى الدعم

Websockets on localhost stopped working in 66.0

Posted

After updating to Firefox 66.0 on MacOS 10.13.6 today, websockets on my localhost stopped working.

When using Create React App (version of "react-scripts": "2.1.8" => "webpack-dev-server": "3.1.14" => "sockjs": "0.3.19"), hot reload is broken and I get following error in the console:

`The connection to ws://localhost:3000/sockjs-node/743/khw0phgj/websocket was interrupted while the page was loading.`

When I tried https://www.websocket.org/echo.html, it works fine and no problems with hot reload in Chrome 72.0.

How can I debug and fix this problem please? (when I googled the error message, I got a lot of outdated advice from previous versions of Firefox)

After updating to Firefox 66.0 on MacOS 10.13.6 today, websockets on my localhost stopped working. When using Create React App (version of "react-scripts": "2.1.8" => "webpack-dev-server": "3.1.14" => "sockjs": "0.3.19"), hot reload is broken and I get following error in the console: `The connection to ws://localhost:3000/sockjs-node/743/khw0phgj/websocket was interrupted while the page was loading.` When I tried https://www.websocket.org/echo.html, it works fine and no problems with hot reload in Chrome 72.0. How can I debug and fix this problem please? (when I googled the error message, I got a lot of outdated advice from previous versions of Firefox)

Modified by Peter Hozák

Chosen solution

No error in 65.0.2 when I downgraded => most likely a bug in Firefox, reported as https://bugzilla.mozilla.org/show_bug.cgi?id=1536843

Read this answer in context 0
Quote

Additional System Details

Installed Plug-ins

  • Shockwave Flash 32.0 r0

Application

  • User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:66.0) Gecko/20100101 Firefox/66.0

More Information

WestEnd
  • Top 25 Contributor
60 solutions 5366 answers

Click the link using Windows 10 and it came up with no progblems and it said also "This Browser Supports WebSocket". So what is the error screenshot saying?

Click the link using Windows 10 and it came up with no progblems and it said also "This Browser Supports WebSocket". So what is the error screenshot saying?
Was this helpful to you? 0
Quote

Chosen Solution

No error in 65.0.2 when I downgraded => most likely a bug in Firefox, reported as https://bugzilla.mozilla.org/show_bug.cgi?id=1536843

No error in 65.0.2 when I downgraded => most likely a bug in Firefox, reported as https://bugzilla.mozilla.org/show_bug.cgi?id=1536843

Modified by Peter Hozák

Was this helpful to you?
Quote

Question owner

WestEnd said

So what is the error screenshot saying?

The error message was in my original post - repeating here if it was hard to notice:


The connection to ws://localhost:3000/sockjs-node/743/khw0phgj/websocket was interrupted while the page was loading.

''WestEnd [[#answer-1206279|said]]'' <blockquote> So what is the error screenshot saying? </blockquote> The error message was in my original post - repeating here if it was hard to notice: The connection to ws://localhost:3000/sockjs-node/743/khw0phgj/websocket was interrupted while the page was loading.
Was this helpful to you?
Quote
cor-el
  • Top 10 Contributor
  • Moderator
17407 solutions 157253 answers

Does toggling this pref on the about:config page make a difference?

  • network.websocket.allowInsecureFromHTTPS
Does toggling this pref on the <b>about:config</b> page make a difference? *network.websocket.allowInsecureFromHTTPS
Was this helpful to you?
Quote

Question owner

cor-el said

Does toggling this pref on the about:config page make a difference?
  • network.websocket.allowInsecureFromHTTPS

nope

''cor-el [[#answer-1206472|said]]'' <blockquote> Does toggling this pref on the <b>about:config</b> page make a difference? *network.websocket.allowInsecureFromHTTPS </blockquote> nope
Was this helpful to you?
Quote
Istoman 0 solutions 1 answers

I can second this is happening only since 66.0 and also on a Vue dev server (so this is not a react-scripts thing).

I can second this is happening only since 66.0 and also on a Vue dev server (so this is not a react-scripts thing).
Was this helpful to you?
Quote
اطرح سؤالا

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.