_blazor websocket error

[khteh]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

ASP.Net Core 6 Scaffold Identity blazor application bumps into websocket error. Firstly, why websocket when my application doesn't need it at all!?! Where is the root cause of this error?

#45453

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

.NET Version

7.0.101

Anything else?

No response

[mkArtakMSFT]

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimalistic repro project that illustrates the problem.

Hi @khteh. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[khteh]

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimalistic repro project that illustrates the problem.

https://learn.microsoft.com/en-us/aspnet/core/security/authentication/scaffold-identity?view=aspnetcore-7.0&tabs=visual-studio#scaffold-identity-into-a-razor-project-with-authorization

https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-tutorial/intro

[mkArtakMSFT]

@khteh your app looks like a Blazor Server app. Blazor Server relies on a websocket connection to work, and that's where you get the WebSocket related messages. If this wasn't intentional, maybe your goal was to start from a Blazor WebAssembly-based application, which would have no requirement for websocket.

As for the error, do you get the same error when you debug / run the application locally? If not, then it's most probably the host that you're using doesn't support websockets.

Hi @khteh. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[khteh]

@khteh your app looks like a Blazor Server app. Blazor Server relies on a websocket connection to work, and that's where you get the WebSocket related messages. If this wasn't intentional, maybe your goal was to start from a Blazor WebAssembly-based application, which would have no requirement for websocket.

As for the error, do you get the same error when you debug / run the application locally? If not, then it's most probably the host that you're using doesn't support websockets.

Running from my local development host does not see this error at all. Only from the same app running in AWS EKS. Is there any specific setup / configuration that needs to be done?

[javiercn]

Running from my local development host does not see this error at all. Only from the same app running in AWS EKS. Is there any specific setup / configuration that needs to be done?

You need to enable sticky sessions on your load balancer. Can you try that and let us know?