blazorr.server.js Error: WebSocket closed with status code: 1006 (no reason given) on IIS server.

Question

blazorr.server.js Error: WebSocket closed with status code: 1006 (no reason given) on IIS server.

40296506 0

Hi everyone, I am developing a .NET 8 Razor Pages web app and I have added a Blazor-server-side component to it.

My app works when I run it in Visual Studio 2022.

However, when I publish it on a local IIS (I have tested it on IIS manager) it works fine (the component works but I got this warning message in the console:

Warning: Failed to connect via WebSockets, using the Long Polling fallback transport. This may be due to a VPN or proxy blocking the connection. To troubleshoot this, visit https://aka.ms/blazor-server-using-fallback-long-polling.

When I publish the app to a real IIS server, the component freezes and I got the following message in the console:

Error: Connection disconnected with error 'Error: WebSocket closed with status code: 1006 (no reason given).'.

Error: Error: WebSocket closed with status code: 1006 (no reason given).

Error: Failed to start the circuit.

Farid Uddin Kiron MSFT 456 Reputation points Microsoft External Staff

2023-12-25T07:57:04.5833333+00:00

Well based on your scenario and error description, it indicates an abnormal closure of the WebSocket connection. Would you kindly make sure WebSockets are enabled in IIS features also

Check for any restrictions or firewall rules that might block WebSocket traffic.
40296506 0 Reputation points

2023-12-26T11:29:52.1666667+00:00

I am sure that Websocket is installed.

Would you please guide me on how to check for any restrictions or firewall rules?
Farid Uddin Kiron MSFT 456 Reputation points Microsoft External Staff

2023-12-28T05:11:43.4833333+00:00

Well, of course I can guide, you can hit windows key + R then type wf.msc in the search bar then hit enter. It should open firewall and advance security options like below:

Check your inbound rules, look for rules specifically allowing WebSocket traffic (TCP port 443 for secure WebSockets, typically). If none exist, create a new inbound rule for WebSockets. In addition, check the outbound rules as well. Please refer to this official document if you need more details.

2 answers

Your answer

Farid Uddin Kiron MSFT 456 Reputation points Microsoft External Staff

2023-12-25T07:57:04.5833333+00:00

Well based on your scenario and error description, it indicates an abnormal closure of the WebSocket connection. Would you kindly make sure WebSockets are enabled in IIS features also

Check for any restrictions or firewall rules that might block WebSocket traffic.
40296506 0 Reputation points

2023-12-26T11:29:52.1666667+00:00

I am sure that Websocket is installed.

Would you please guide me on how to check for any restrictions or firewall rules?
Farid Uddin Kiron MSFT 456 Reputation points Microsoft External Staff

2023-12-28T05:11:43.4833333+00:00

Well, of course I can guide, you can hit windows key + R then type wf.msc in the search bar then hit enter. It should open firewall and advance security options like below:

Check your inbound rules, look for rules specifically allowing WebSocket traffic (TCP port 443 for secure WebSockets, typically). If none exist, create a new inbound rule for WebSockets. In addition, check the outbound rules as well. Please refer to this official document if you need more details.

Answer 1

AgaveJoe 30,126

Are Web Sockets installed on the server?

IIS 8.0 WebSocket Protocol Support

40296506 0 Reputation points

2023-12-26T08:36:41.0433333+00:00

Yes I have confirmed that the Websocket is installed.

Answer 2

Bruce (SqlWork.com) 77,686 Volunteer Moderator

The server message says the server can not open a websocket, so it falling back to signalr polling.

the client code has probably been configured to only support websockets.

as suggested you need to enable websockets on the server, or enable long polling on the client.

40296506 0 Reputation points

2023-12-26T08:41:55.01+00:00

Websocket is installed in the server.

Could you please elaborate more on how to enable long polling on the client?

Share via

blazorr.server.js Error: WebSocket closed with status code: 1006 (no reason given) on IIS server.

2 answers

Your answer