DEV Community 👩‍💻👨‍💻

John Peters
John Peters

Posted on • Updated on

SignalR ERR_CONNECTION_REFUSED Using ASP.NET Core 3.1 (make sure server is up)

When the scaffolding for both client and server is set up for SignalR. The first thing on the client side is to attempt to connect to the Hub.

Negotiate Error

Our first attempt to connect to the server hub.

Alt Text


Alt Text

//But chrome showed this

Request URL: https://localhost:8081/Hub/ClientStatus/negotiate

Response: XHR negotiate (failed) ERR_CONNECTION_REFUSED xhr

Enter fullscreen mode Exit fullscreen mode

The root cause of this days long error was that you cannot use the old signalr client libraries found in ASP.NET.

// do not use this one in a .net core application!
npm i
// Use this one.
npm i @microsoft/signalr
Enter fullscreen mode Exit fullscreen mode


Make sure your server is up an running. If negotiation attempts show red, nobody is responding!

JWP2020 npm i @microsoft/signalr

Top comments (0)

🌚 Browsing with dark mode makes you a better developer.

It's a scientific fact.