Skip to content

Net 6 Blazor server application::Failed to start the transport 'WebSockets': Error: WebSocket failed to connect. The connection could not be found on the server, either the endpoint may not be a SignalR endpoint, the connection ID is not present on the server, or there is a proxy blocking WebSockets. If you have multiple servers check that sticky sessions are enabled. #43175

@rajaashutosh

Description

@rajaashutosh

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

I am running the .Net 6 Blazor server application. The application is working fine in localhost/ with a single instance. However, when I deployed to a pivotal cloud foundry with multiple instances it starts breaking.

With a single instance, its page loads look fine.

With multiple instances, the page is showing blank. please refer to the screenshot.
image

image

Error:
[2022-08-09T20:26:06.460Z] Error: Failed to start the transport 'WebSockets': Error: WebSocket failed to connect. The connection could not be found on the server, either the endpoint may not be a SignalR endpoint, the connection ID is not present on the server, or there is a proxy blocking WebSockets. If you have multiple servers check that sticky sessions are enabled.

Also after a couple of refresh pages showing up, again if I start to navigate to other links its kind of not working.

Expected Behavior

Page should up and running with multiple instances

Steps To Reproduce

No response

Exceptions (if any)

Not using any Nginx rule for now. the deployment env is Linux

.NET Version

6

Anything else?

ASP.NET Core version 6

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions