Signalr client side functions not being called when hosted in IIS

Question

I have a signal r application that is working in visual studio, locally, but when I publish to IIS 7 in my local machine, it runs fine. but my signal client callback functions, ain't receiving any calls from the hub class on the server.

I don't know what are the possible reasons for this?

Kishore Sahasranaman · Answer 1 · 2015-10-23T13:46:18.507

0

You need to install Web Sockets in the machine.

To enable support for the WebSocket Protocol on Windows Server 2012, use the following steps:

Open Server Manager.
Under the Manage menu, click Add Roles and Features.
Select Role-based or Feature-based Installation, and then click Next.
Select the appropriate server, (your local server is selected by default), and then click Next.
Expand Web Server (IIS) in the Roles tree, then expand Web Server, and then expand Application Development.
Select WebSocket Protocol, and then click Next.
If no additional features are needed, click Next.
Click Install.
When the installation completes, click Close to exit the wizard.

When the installation completes, click Close to exit the wizard.

http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-websocket-protocol-support

Windows 8 :

Click the Windows button
Type: Turn windows features on or off
Navigate to: Internet Information Services > World Wide Web services > Application Development Features
Select “Websocket Protocol” + OK

edited Oct 23 '15 at 13:46

answered Oct 23 '15 at 12:51

Kishore Sahasranaman

4,013
3
24
50

Because I'm using windows 8, I had to turn on IIS WebSocket Protocol feature. However this hasn't work. http://www.codeguru.com/csharp/csharp/programming-html5-web-sockets-in-asp.net-4.5.htm – Abdul Rahaman Abdullah Oct 23 '15 at 13:30
Try registering the asp.net with iis .. http://stackoverflow.com/a/647609/2074346 – Kishore Sahasranaman Oct 23 '15 at 13:49
Signalr should fall back to non-websockets transports if they aren't available, I believe. I.e. from the [Introduction to SignalR](http://www.asp.net/signalr/overview/getting-started/introduction-to-signalr): "SignalR uses the new WebSocket transport where available, and falls back to older transports where necessary" – Damien_The_Unbeliever Oct 23 '15 at 13:59
I'm running .net4.5, and this is turned on, IIS in windows Features – Abdul Rahaman Abdullah Oct 23 '15 at 14:03
I've included this line of code, but still no luck. connection.start({ transport: ['webSockets'] }) – Abdul Rahaman Abdullah Oct 23 '15 at 14:27

Signalr client side functions not being called when hosted in IIS

1 Answers1