How to debug websocket connection error with "Unknown reason"

Question

Recently, I am getting the following message on chrome console;

WebSocket connection to 'ws://evo15:4008/?stream' failed: Unknown reason

It's getting more and more and it's somehow annoying and I have to open a new tab or restart chrome every time to get back to normal websocket connection. How can I debug it? Unfortunately, I cannot reproduce it yet. My chrome version is Version 77.0.3865.75 (Official Build) (64-bit)

Update 1: I think you could reproduce it by closing the connection for a long time (I don't know the exact time) from server side and then open it and try to connect to it (client trys to connect every 1 sec). Then it will happen. So I guess there is an expire time or a limited number of tries to connect somewhere.

Update 2: It happens after 256 tries of reconnection.

WebSocket connection to 'ws://evo15:4008/?stream' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

After seeing 255 of this error on console, you will see the first error and cannot reconnect. So I think there is a 8 bit limit somewhere that I am missing

Are you spying on my development workstation? I have been scratching my head over the same question. Your clue about the suspicious number inspired me to write this jsBin for investigating this. — jacobq
– jacobq, Commented Sep 20, 2019 at 16:57
Another clue that I have found (using the aforementioned script) is that taking a Heap Snapshot (Dev Tools -> Memory) shows that WebSocket objects persist despite refreshing the page. — jacobq
– jacobq, Commented Sep 20, 2019 at 17:16
Firefox appears to have a similar limit (200) but it seems to reset after the page is refreshed. — jacobq
– jacobq, Commented Sep 20, 2019 at 17:47
@Gokigooooks not yet. Please login in the bug page and star it. That would help — Reza
– Reza, Commented Oct 2, 2019 at 6:15

sshmaxime · Accepted Answer · 2020-08-31 22:50:24Z

25

For some very very very odd reason in my computer the websocket connection was considered as an ad by AdBlock.

Try to disable AdBlock and see if it works.

answered Aug 31, 2020 at 22:50

sshmaxime

5378 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Nauman Moazzam Over a year ago

Saved the day bro!

jacobq · Accepted Answer · 2019-11-27 14:59:04Z

24

Looks like someone just filed this as a Chromium (v77) bug. See issue tracking it here.

Update 1: As noted in the issue tracker and comments below, this should now be fixed in the latest stable release, which is being rolled out now (2019/10/11).

Update 2: Despite the bug being marked as fixed/closed in monorail, canary (80.0.3977.4) still appears to have this behavior. As others have noted there is a global limit of 255. However, the fact that connections opened by JS don't get closed/reset when the page is refreshed still seems like a bug to me.

edited Nov 27, 2019 at 14:59

answered Sep 20, 2019 at 17:58

jacobq

11.6k4 gold badges44 silver badges73 bronze badges

2 Comments

Reza Over a year ago

Yeah. I suspected that it may be a bug in chromium. Let's see when they fix it :)

Rupert Rawnsley Over a year ago

Apparently the fix is rolled out now: bugs.chromium.org/p/chromium/issues/detail?id=1006243#c42

Collectives™ on Stack Overflow

How to debug websocket connection error with "Unknown reason"

2 Answers 2

1 Comment

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related