X
Nhấn vào đây để đến phiên bản di động của trang web.

Diễn đàn trợ giúp

Websockets on localhost stopped working in 66.0

Được đăng

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)

Được chỉnh sửa bởi Peter Hozák vào

Giải pháp được chọn

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

Đọc câu trả lời này trong ngữ cảnh 0

Chi tiết hệ thống bổ sung

Phần bổ trợ đã cài đặt

  • Shockwave Flash 32.0 r0

Ứng dụng

  • Chuỗi đại diện người dùng: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:66.0) Gecko/20100101 Firefox/66.0

Thông tin chi tiết

WestEnd 60 giải pháp 5387 câu trả lời
Được đăng

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?

Giải pháp được chọn

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

Được chỉnh sửa bởi Peter Hozák vào

Người tạo câu hỏi

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
17573 giải pháp 158962 câu trả lời
Được đăng

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

Người tạo câu hỏi

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 giải pháp 1 câu trả lời
Được đăng

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