X
Tocca qui per la versione per piattaforma mobile del sito.

Forum di supporto

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Websockets on localhost stopped working in 66.0

Inserita

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)

Modificato da Peter Hozák il

Soluzione scelta

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

Leggere questa risposta nel contesto 0

Dettagli aggiuntivi sul sistema

Plugin installati

  • Shockwave Flash 32.0 r0

Applicazione

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

Ulteriori informazioni

WestEnd 60 soluzioni 5387 risposte

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?

Soluzione scelta

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

Modificato da Peter Hozák il

Utente che ha posto la domanda

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.
cor-el
  • Top 10 Contributor
  • Moderator
17578 soluzioni 159013 risposte

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

Utente che ha posto la domanda

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
Istoman 0 soluzioni 1 risposte

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).