Blazor javascript error

Nobody has claimed this yet.

Greetings all,

I upgraded. (Linux Server, I am using Brave to access the system)

Logged into the remotely system. Staring at the *devices* page, I open up the web developer toolbar to review some code (ctrl + shift + I )

I see this javascript error:

WebSocket connection to 'ws://(removed ip address:port#)/_blazor?id=oewSp6WI0YO2wOipCSvOQQ' failed:
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
q @ blazor.server.js:1
e.connect @ blazor.server.js:1
e.startTransport @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
G @ blazor.server.js:1
e.createTransport @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
a @ blazor.server.js:1

[2021-11-13T18:08:51.588Z] Error: Failed to start the transport 'WebSockets': Error: There was an error with the transport.
e.log @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
s @ blazor.server.js:1
Promise.then (async)
c @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
G @ blazor.server.js:1
e.createTransport @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
a @ blazor.server.js:1
Promise.then (async)
c @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
G @ blazor.server.js:1
e.startInternal @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
G @ blazor.server.js:1
e.start @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
k @ blazor.server.js:1
e.startInternal @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
k @ blazor.server.js:1
e.startWithStateTransitions @ blazor.server.js:1
e.start @ blazor.server.js:1
(anonymous) @ blazor.server.js:10
(anonymous) @ blazor.server.js:10
(anonymous) @ blazor.server.js:10
(anonymous) @ blazor.server.js:10
r @ blazor.server.js:10
C @ blazor.server.js:10
(anonymous) @ blazor.server.js:10
(anonymous) @ blazor.server.js:10
(anonymous) @ blazor.server.js:10
(anonymous) @ blazor.server.js:10
r @ blazor.server.js:10
S @ blazor.server.js:10
(anonymous) @ blazor.server.js:10
n @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
(anonymous) @ blazor.server.js:1
Show 22 more frames

Remotely Version:
Version: 2021.08.26.1335

Desktop:
OS: Linux pop-os
browser: Brave
Version: Linux pop-os 5.13.0-7614-generic #14~1631647151~21.04~930e87c-Ubuntu SMP Fri Sep 17 00:24:58 UTC x86_64 x86_64 x86_64 GNU/Linux

Expected behavior: No Javascript error.

Context:

If I attempt to remote into one of the clients: A new tab opens, named 'undefined', no remote screen shows. However, I do control the mouse and what-not on the remote screen. I just cannot see it. A javascript error appears on this particular page, as well, which made me retrace my steps to the page after logging in.

Start by reproducing the failure from the Devices page and the remote-client tab, then inspect the WebSocket errors reported by blazor.server.js in Brave's developer tools. Done means the page no longer reports the failed WebSockets transport and the remote screen is visible in the new tab while mouse control continues to work.

Written by the indexing model from the issue text.