This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 20%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETB%3C/text%3E%3C/svg%3E)
My Blazor web site starts up but when go to a page is gives me an error.
[2024-06-14T15:20:27.225Z] Information: Normalizing '_blazor' to 'https://fieldmriservice.azurewebsites.net/_blazor'.
blazor.server.js:1 [2024-06-14T15:20:27.370Z] Information: WebSocket connected to wss://fieldmriservice.azurewebsites.net/_blazor?id=hWxuOAUI3-5ZBYRAp4as2g.
blazor.server.js:1 [2024-06-14T15:20:29.531Z] Error: There was an unhandled exception on the current circuit, so this circuit will be terminated. For more details turn on detailed exceptions by setting 'DetailedErrors: true' in 'appSettings.Development.json' or set 'CircuitOptions.DetailedErrors'.
[2024-06-14T15:20:27.225Z] Information: Normalizing '_blazor' to 'https://fieldmriservice.azurewebsites.net/_blazor'.
blazor.server.js:1 [2024-06-14T15:20:27.370Z] Information: WebSocket connected to wss://fieldmriservice.azurewebsites.net/_blazor?id=hWxuOAUI3-5ZBYRAp4as2g.
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
It will run fine in Visual Studio 2022
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
@Thomas Blair , just checking in to see if you had got a chance to see the previous response.
Kindly share the solution that worked for you. I'll summarize it to benefit the community Or please share the requested/more info to help you better.
@Thomas Blair , Apologies for the delayed response.
I see that your WebApp is published and rendering correctly. Kindly share the solution that worked for you. I'll summarize it to benefit the community.
If you need any further assistance, please let us know, we will be more than happy to assist you.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 16%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EY1%3C/text%3E%3C/svg%3E)
I am also facing the same issue. Thomas, Please let me know if you found any solution for this.
YachamaneniSreelekha-1920, Apologies for the delayed response.
To fetch more details, you may view the Application event Logs, checkout this doc for more details: #application-event-log-azure-app-service
Just to highlight, hosting a Blazor Web App that uses interactive server-side rendering on Azure App Service requires configuration for Application Request Routing (ARR) affinity and WebSockets. The App Service should also be appropriately globally distributed to reduce UI latency.
We recommend using WebSockets for server-side Blazor apps deployed to Azure App Service. Host and deploy server-side Blazor apps
Here is the detailed explanation of the issue.My blazor app works fine in local. I had deployed the code to Azure and did front door configuration. For lower environments, its showing warning message and it is working as expected without web sockets. (As I believe Front door does not support web sockets - correct me if I am wrong?)
I followed the same process for production environment too but getting below errors. And any click action is not working.
Can you please help me ASAP? Thank you!
Hi ajkuma, Here is the detailed explanation of the issue.
My Blazor app works perfectly in local. I had deployed the app to azure and did front door configuration. For lower environments it is working as expected. Just getting warning message when I hit the front door externalized URL.
I have followed same process for production environment. With App service default domain URL is working as expected but not with the front door externalized URL.
Here is the issue that I am getting
Note: For lower/ production env's not using websockets but the lower env's working fine but not the production one. (I believe front door does not support web sockets, correct me if I am wrong?)
Can you please help me out asap. Thank you!
Apologies for the delayed response from over the weekend. If it's fine, could you please share your WebApp name here.
If you have a support plan, please file a support ticket for a dedicated, specialized and immediate assistance.