Asp .Net Core 2 + SignalR (1.0.0-alpha2-27025) + /signalr/negotiate 404 Error

Question

I add SignalR to ASP .Net Core 2 app

packages

"Microsoft.AspNetCore.All" Version="2.0.0"
"Microsoft.AspNetCore.SignalR" Version="1.0.0-alpha2-27025"
"Microsoft.AspNetCore.SignalR.Client" Version="1.0.0-alpha2-27025"
"Microsoft.AspNetCore.SignalR.Client.Core" Version="1.0.0-alpha2-27025"
"Microsoft.AspNetCore.SignalR.Common" Version="1.0.0-alpha2-27025"
"Microsoft.AspNetCore.SignalR.Core" Version="1.0.0-alpha2-27025"

public IServiceProvider ConfigureServices(IServiceCollection services)
{
    services.AddSignalRCore();
    services.AddSignalR();
}

and

public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory, IServiceProvider serviceProvider)
    app.UseSignalR(routes =>
    {
        routes.MapHub<ManageHub>("manageHub");
    });
}

url:port/signalr, url:port/signalr/negotiate... return 404

url:port/manageHub return 400 with "Connection ID required"

I not found .MapSignalR()

How use SignalR in ASP .Net Core?

have you tried testing it using a client side code? I guess the signalr client libraries would take care of the clientID etc — Neville Nazerane
Man you are keen tackling an alpha. I'm hanging out for the team to get the core version running too. I'll be interested to see if anyone is keen to post anything this early. — OrdinaryOrange
OrdinaryOrange yes I too was scared of the alpha and created an .net framework website just for signalr. But at least the set up should still work, or they wouldn't have released it — Neville Nazerane

Pawel Pawel · Accepted Answer · 2017-09-18T00:05:22

You seem to be using the old client. SignalR for ASP.NET Core does not use the /negotiate endpoint anymore. The new SignalR server is not compatible with old client and the new clients are not compatible with the old SignalR server. Take a look at the announcement and samples

Asp .Net Core 2 + SignalR (1.0.0-alpha2-27025) + /signalr/negotiate 404 Error

2 Answers