Trying standard why of ASP.NET Core 5 Signalr and Angular but it is showing error in console .error : websocket failed to connect [closed]

Question

Closed. This question needs debugging details. It is not currently accepting answers.

Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.

Closed 4 months ago.

Improve this question

I'm trying to use SignalR in ASP.NET Core 5; I've added SignalR service in service configuration and also created a hub class and its method with Angular, which is also configured as I saw on another website. Their code is similar but I am still getting below error:

Error: Failed to start the connection:
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.

halfer · Accepted Answer · 2025-07-26 13:41:49Z

1

For four days I was facing issue in Signalr configuration but the error issue reason was port number.

Incidentally I changed my port number from application properties (Debug Properties) but forgot to change the application path in Angular SignalR configuration which was not showing any cores issue.

I changed Angular SignalR Configuration withUrl path to right path and the issue was resolved.

edited Jul 26 at 13:41

halfer

20.2k20 gold badges110 silver badges207 bronze badges

answered Sep 4, 2022 at 5:50

Ravi

193 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Trying standard why of ASP.NET Core 5 Signalr and Angular but it is showing error in console .error : websocket failed to connect [closed]

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related