StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>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.</p> <p>First you need to add this code to the Startup.cs:</p> <pre><code>var hubConfiguration = new HubConfiguration(); hubConfiguration.EnableDetailedErrors = true; app.MapSignalR(hubConfiguration); </code></pre> <p>Then to show the error on the client side you need to add this code to your project:</p> <pre><code>$.connection.hub.error(function (error) { console.log('SignalR error: ' + error) }); </code></pre> <p>As simple as that and you're good to go.</p> <p>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.</p> <p>This is a sample debug with Chrome Browser for people who what to see SignalR errors through Chrome debug tool:</p> <p><a href="https://i.stack.imgur.com/MngYB.jpg" rel="noreferrer">Download Full Image Size</a></p> <p><img src="https://i.stack.imgur.com/MngYB.jpg" alt="This is for people who want to debug the ajax response through Chrome Browser"></p> <p>Let me know if you have other problems regarding that.</p> <p>For extra information go to: <a href="http://www.asp.net/signalr/overview/signalr-20/hubs-api/hubs-api-guide-javascript-client#handleerrors" rel="noreferrer">SignalR Errors</a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload