Blazor serverside SignalR issue after upgrading to 3.0.100-rc1-014190
See original GitHub issueUpgrading dotnet sdk to 3.0.100-rc1-014190 causes an issue with SignalR:
How to reproduce:
- Install new sdk 3.0.100-rc1-014190 binaries on Ubuntu
- Create a new blazor serverside project: dotnet new blazorserver -au individual
- Start the app: dotnet run
- Navigate to https://localhost:5001/ and check the browser’s console, you will see:
[2019-09-17T14:19:04.940Z] Information: Normalizing '_blazor' to 'https://codescu.com/_blazor'. blazor.server.js:1:5212
Firefox nu poate stabili o conexiune cu serverul wss://codescu.com/_blazor?id=hm6jAVLCWc4yC4eZqxWerQ. blazor.server.js:1:37545
[2019-09-17T14:19:05.587Z] Error: Failed to start the transport 'WebSockets': Error: There was an error with the transport. blazor.server.js:1:5015
[2019-09-17T14:19:05.597Z] Warning: Call to HttpConnection.stopConnection(Error: WebSocket closed with status code: 1006 ().) was ignored because the connection hasn't yet left the in the connecting state. blazor.server.js:1:5112
[2019-09-17T14:19:05.738Z] Error: Failed to start the transport 'LongPolling': TypeError: this.transport is undefined blazor.server.js:1:5015
[2019-09-17T14:19:05.741Z] Error: Failed to start the connection: Error: Unable to connect to the server with any of the available transports. WebSockets failed: Error: There was an error with the transport. ServerSentEvents failed: Error: 'ServerSentEvents' does not support Binary. LongPolling failed: TypeError: this.transport is undefined blazor.server.js:1:5015
[2019-09-17T14:19:05.751Z] Error: Error: Unable to connect to the server with any of the available transports. WebSockets failed: Error: There was an error with the transport. ServerSentEvents failed: Error: 'ServerSentEvents' does not support Binary. LongPolling failed: TypeError: this.transport is undefined blazor.server.js:15:27313
Error: Cannot send data if the connection is not in the 'Connected' State. blazor.server.js:1:42087
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Blazor is NOT loosing SignalR connection. Browser is!
I believe it is because after some time the state of the connection on a server side gets disposed, thus there is nothing...
Read more >Blazor Server client side with SignalR doesn't work
The issue is that the SignalR connection between the browser and Blazor Server is becoming disconnected. When this happens, the browser will ...
Read more >ASP.NET Core Blazor SignalR guidance
This article explains how to configure and manage SignalR connections in Blazor apps. Throughout this article, the terms client/client-side ...
Read more >Instantly Update a Real-Time Chart with SignalR in Blazor ...
In this blog, we will learn how to create and update a real-time chart in a Blazor server-side app using SignalR communication.
Read more >Let's Learn Blazor: Blazor Server with SignalR
Running our Blazor Server. If you've created and started a Blazor WASM app, then starting a server-side Blazor app is actually unremarkable.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Allowing websockets on the proxy solved this issue.
Thank you.
Similar issue here - but no way to permit WebSockets: #14613