Quantcast
Channel: Active questions tagged blazor - Stack Overflow
Viewing all articles
Browse latest Browse all 4839

Set my app server to 2 servers, getting a _blazor load error

$
0
0

My Blazor server app runs fine on Azure with one server. When I scale it out to two servers, I sometimes get the following. I have session affinity turned off. This clearly is the Blazor framework having problems. Any idea why?

Update: I turned on session affinity and the problem is gone. Does Blazor server require affinity so that it can have a series of system files like blazor.server.js all be read from the same server?

[2024-06-01T14:56:43.408Z] Information: Normalizing '_blazor' to 'https://louishowe-dev.azurewebsites.net/_blazor'.blazor.server.js:1 GET https://louishowe-dev.azurewebsites.net/_blazor?id=gc8YOVE1nE_g8k914Nk3ng&_=1717253803473 404 (Not Found)send @ blazor.server.js:1send @ blazor.server.js:1send @ blazor.server.js:1get @ blazor.server.js:1connect @ blazor.server.js:1_startTransport @ blazor.server.js:1_createTransport @ blazor.server.js:1_startInternal @ blazor.server.js:1await in _startInternal (async)start @ blazor.server.js:1_startInternal @ blazor.server.js:1_startWithStateTransitions @ blazor.server.js:1start @ blazor.server.js:1startConnection @ blazor.server.js:1startCore @ blazor.server.js:1start @ blazor.server.js:1Pr @ blazor.server.js:1await in Pr (async)Ar @ blazor.server.js:1Br @ blazor.server.js:1(anonymous) @ blazor.server.js:1(anonymous) @ blazor.server.js:1(anonymous) @ blazor.server.js:1blazor.server.js:1 [2024-06-01T14:56:43.545Z] Error: Failed to start the transport 'LongPolling': Error: No Connection with that ID: Status code '404'log @ blazor.server.js:1_createTransport @ blazor.server.js:1await in _createTransport (async)_startInternal @ blazor.server.js:1await in _startInternal (async)start @ blazor.server.js:1_startInternal @ blazor.server.js:1_startWithStateTransitions @ blazor.server.js:1start @ blazor.server.js:1startConnection @ blazor.server.js:1startCore @ blazor.server.js:1start @ blazor.server.js:1Pr @ blazor.server.js:1await in Pr (async)Ar @ blazor.server.js:1Br @ blazor.server.js:1(anonymous) @ blazor.server.js:1(anonymous) @ blazor.server.js:1(anonymous) @ blazor.server.js:1blazor.server.js:1 [2024-06-01T14:56:43.545Z] Error: Failed to start the connection: Error: Unable to connect to the server with any of the available transports. ServerSentEvents failed: Error: 'ServerSentEvents' does not support Binary. Error: LongPolling failed: Error: No Connection with that ID: Status code '404'log @ blazor.server.js:1_startInternal @ blazor.server.js:1await in _startInternal (async)start @ blazor.server.js:1_startInternal @ blazor.server.js:1_startWithStateTransitions @ blazor.server.js:1start @ blazor.server.js:1startConnection @ blazor.server.js:1startCore @ blazor.server.js:1start @ blazor.server.js:1Pr @ blazor.server.js:1await in Pr (async)Ar @ blazor.server.js:1Br @ blazor.server.js:1(anonymous) @ blazor.server.js:1(anonymous) @ blazor.server.js:1(anonymous) @ blazor.server.js:1blazor.server.js:1 [2024-06-01T14:56:43.545Z] Error: Error: Unable to connect to the server with any of the available transports. ServerSentEvents failed: Error: 'ServerSentEvents' does not support Binary. Error: LongPolling failed: Error: No Connection with that ID: Status code '404'log @ blazor.server.js:1unhandledError @ blazor.server.js:1startConnection @ blazor.server.js:1await in startConnection (async)startCore @ blazor.server.js:1start @ blazor.server.js:1Pr @ blazor.server.js:1await in Pr (async)Ar @ blazor.server.js:1Br @ blazor.server.js:1(anonymous) @ blazor.server.js:1(anonymous) @ blazor.server.js:1(anonymous) @ blazor.server.js:1blazor.server.js:1 [2024-06-01T14:56:43.545Z] Error: Failed to start the circuit.

Viewing all articles
Browse latest Browse all 4839

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>