Clearly you have some problems on the server side. But to find out what's the problem you need to see a detailed error.
For security reasons SignalR doesn't give you a detailed error by default. But you can edit your code to get the detailed error.
First you need to add this code to the Startup.cs:
var hubConfiguration = new HubConfiguration();
hubConfiguration.EnableDetailedErrors = true;
app.MapSignalR(hubConfiguration);
Then to show the error on the client side you need to add this code to your project:
$.connection.hub.error(function (error) {
console.log('SignalR error: ' + error)
});
As simple as that and you're good to go.
Sometimes you don't even get to the client part to see the error. But by doing the first part you'll enable the Detailed Error and you can see the errors on the SignalR response. You just need a tool like Chrome Browser Web Developer Tool which gives you the Network part of the operation where all the data transfer status are logged. you can check the SignalR errors there. The information on the log will be very detailed and helpful.
This is a sample debug with Chrome Browser for people who what to see SignalR errors through Chrome debug tool:
Download Full Image Size
Let me know if you have other problems regarding that.
For extra information go to: SignalR Errors
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…