Problem "WebSocket connection to '<URL>' failed: WebSocket is closed before the connection is established.". Only browser restart helps

[yshurik]

Description

Brave no doubt has problems with websocket system.
Web sites which are in use continuous (like to stay open some hours) usually got into "broken" websocket mode.
In dev console it is indicated by message:

WebSocket connection to '<URL>' failed: WebSocket is closed before the connection is established.

When it gots into this mode, then nothing help

1. close and reopen website - does not help
2. open new window to the website- does not help
3. switch on/off brave shields - does not help
4. only help - complete quit of brave and start it from scratch

Steps to Reproduce

1. open web site using websockets
2. wait for hours (hard to determine how much, but usually web site with web sockets does not work if left over night open)
3. see in dev console WebSocket connection to '<URL>' failed: WebSocket is closed before the connection is established.

Actual result:

No working web sockets system at all

Expected result:

Web sockets working like in chrome, firefox etc

Reproduces how often:

Every days, after some hours of opened web site with web sockets

Brave version (brave://version info)

Version 1.31.87 Chromium: 95.0.4638.54 (Official Build) unknown (64-bit)

Also can confirm same on latest Brave on Mac OSX

Version/Channel Information:

• Can you reproduce this issue with the current release? - yes
• Can you reproduce this issue with the beta channel? - i do not know
• Can you reproduce this issue with the nightly channel? - i do not know

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields? - no
• Does the issue resolve itself when disabling Brave Rewards? - no
• Is the issue reproducible on the latest version of Chrome? - no

Miscellaneous Information:

web sockets are useful system to have site staying long time without need to reload but in case of Brave it needs the full browser restart :(

[wanton7]

I think this duplicate of #15410 that is somehow marked as repros-on-chrome even when it's not happening in Chrome.

[altdsoy]

I have the same weird problem..
But the sad part in my case it's that restarting Brave (and even the computer) does not solve the problem..
And it's happening for only one website (in my case localhost:4000)