Signalr/Hub not loading in IIS 7 but working correctly in Visual Studio

Asked 8/11, 2011 at 15:53 Answered 17/5, 2020 at 1:25

I am working on a Web Application on the Asp .Net 4.0 framework that uses SignalR, having installed it from the Nuget package. When I debug or run the application without debugging locally it works correctly. However, when it is deployed to the production server it is unable to find the signal/hubs file that is being dynamically injected into the httphandlers. Due to it's dynamic nature it has to be created on the fly, so I can't just copy the working file into the project either.

I have tried the following methods of loading the file:

<script src="/signalr/hubs" type="text/javascript"></script>
<script src="signalr/hubs" type="text/javascript"></script>

And in the code behind:

ScriptManager.GetCurrent(Page).Scripts.Add(new ScriptReference("~/signalr/hubs"));

All of these work locally but not on the server. The path that is rendered in the html looks correct, but there is no file there, delivering a 404 error. If it matters, the server has given the application Full Trust and the application is being run as an application under another site in IIS that uses a subdomain.

Horowitz answered 8/11, 2011 at 15:53 Comment(2)

I am experiencing the same issue as well. I seems to get it working on IIS7 and not IIS6 though – Hafiz 8/11, 2011 at 16:31

This isn't working in IIS7 for us, though IIS6 is installed on the server. IIS6 is only handling the mail however, not the site – Horowitz 20/9, 2012 at 13:33

The problem was solved by setting the following flags in the web.config.

<configuration>
    <system.webServer>
        <validation validateIntegratedModeConfiguration="false" />
        <modules runAllManagedModulesForAllRequests="true">
        </modules>
    </system.webServer>
</configuration>

For some reason Nuget did not set these values for Elmah or SignalR

Horowitz answered 9/11, 2011 at 14:10 Comment(7)

Thanks for sharing the solution, it saves my several hours. my scene is serer can't send message to clent. – Iva 26/4, 2013 at 4:54

@PCasagrande:- I am having similar problem ..i tried all the things suggested above but no luck..Any help will be appreciable.I am using IIS 5.1 and windows XP. – Skinnydip 12/8, 2013 at 10:19

@Skinnydip did you install using Nuget? That should do most of the heavy lifting for you. Do you get a 404 error when you navigate to the /signalr/hubs url? – Horowitz 13/8, 2013 at 15:10

Yes i installed using Nuget and i get 404 error while navigating to /signalr/hubs. – Skinnydip 14/8, 2013 at 5:35

Yess! after a few hours, i found this and now it works. Could you explain why we needed those props? – Mollescent 30/9, 2013 at 0:8

I think it was runAllManagedModulesForAllRequests that really fixed things. Basically it turns on the modules that can intercept requests and process them in some way. They are what make .aspx pages do things for example. Here it intercepts the request for a file that doesn't exist and runs the code that ends up creating the output. An explanation is located at #11049363 – Horowitz 2/10, 2013 at 0:18

I used <script src="<%: ResolveUrl("~/signalr/hubs") %>"></script> and it worked. – Hydrostatic 8/2, 2014 at 6:28

I was facing a similar issue, I just changed the /signalr/hubs to /virtualDirectoryName/signalr/hubs and it worked.

Footpath answered 19/9, 2012 at 13:14 Comment(1)

I replaced <script src="/signalr/hubs"></script> with <script src="signalr/hubs"></script> I removed the leading slash to make it a relative path instead of a rooted path. – Traceytrachea 26/1, 2016 at 7:11

Replace:

<script src="/signalr/hubs" type="text/javascript"></script>

with:

<script src="<%= ResolveUrl("~/signalr/hubs") %>" type="text/javascript"></script>

Chatterjee answered 8/11, 2011 at 16:46 Comment(8)

This did not work. It outputs the same path as the ScriptManager code I tried, which does not resolve. – Horowitz 8/11, 2011 at 16:50

@PCasagrande, I assume your application is hosted in a virtual directory, so the correct path would be /appname/signalr/hubs. Normally the ResolveUrl method takes into account the virtual directory name. – Chatterjee 8/11, 2011 at 16:56

It is being run as an application under a site, so yes the appname is required. ResolveUrl does address that, but so does the tilde in server side code. The path looks correct, but the file is not there. – Horowitz 8/11, 2011 at 18:21

So what is the resulting url in your browser after using ResolveClientUrl? Does it still return a 404 then? Are you writing an MVC application? Can you hit other extensionless urls in your application? – Biddick 9/11, 2011 at 3:22

@dfowler, It is a Web Forms Web Application. The path it is generating is /HostingCenterStatus/signalr/hubs which sends the request to subdomain.domain.com/HostingCenterStatus/signalr/hubs and it returns a 404 error. All of the pages are default.aspx that are navigated to by just using the folder name. – Horowitz 9/11, 2011 at 13:47

@PCasagrande, are you running the application in Integrated Mode in IIS? Or is it Classic Mode? – Chatterjee 9/11, 2011 at 13:48

I found the problem and am posting the solution. There were some missing web.config settings. I don't know why it works in Visual Studio without them, but it is working now. – Horowitz 9/11, 2011 at 14:8

Thank you!! Saved my bacon. It was driving me nuts why my hub code wasn't running. – Papillose 11/11, 2014 at 1:17

You Js file should be include like this :

<script src="~/Scripts/jquery.signalR-2.1.1.js"></script>
<script src="~/signalr/hubs"></script>

Randallrandan answered 25/4, 2016 at 10:57 Comment(1)

All the tilde does is say it is affecting the root of the website. The URLs generated were the same. It was an issue with the handlers not firing for the requests. The problem was solved below. – Horowitz 4/5, 2016 at 18:56

In our case we had issue with optimizeCompilations attribute in web.config (http://msdn.microsoft.com/en-us/library/ms366723.aspx). Removing optimizeCompilations from web.config solved issue.

Clevis answered 22/2, 2012 at 13:32 Comment(0)

The above is the answer for this one but I want to point out if you already have URL Rewriting for generic rules which I did and I was confused as to my 404 issue that was not solved by this one, I added the following rule to overwrite my greedy matching that was causing the 404 for URL Rewrite.

<rule name="signalR" stopProcessing="true">
    <match url="^signalr.*" />
    <action type="None" />
</rule>
<!-- greedier rules below -->

This is just here in case someone has a similar issue.

Wirephoto answered 27/12, 2011 at 7:8 Comment(0)

I noticed @PCasagrande mentioned in one of the comments that this problem was on a subdomain site.

I had a similar problem and added a rewrite rule to remove the application folder from the url. This solved my 404 error on 'signalr/hubs':

<rule name="Remove SubDomain folder from url" stopProcessing="false">
    <match url="^(.*)SubDomain/(.*)$" />
    <conditions logicalGrouping="MatchAll" trackAllCaptures="false" />
    <action type="Rewrite" url="{R:1}{R:2}" />
</rule>

I added the 'remove subdomain' rule before the rewrite rule for the subdomain:

<rule name="Redirect subdomain.domain.com to SubDomain folder" enabled="true">
    <match url="^(.*)$" />
    <conditions logicalGrouping="MatchAll" trackAllCaptures="false">
        <add input="{HTTP_HOST}" pattern="^subdomain\.domain\.com$" />
    </conditions>
    <action type="Rewrite" url="/SubDomain/{R:0}" />
</rule>

Schnitzel answered 12/3, 2012 at 9:5 Comment(0)

I am also using a subdomain. When using SignalR 0.5.3, I had to modify the web.config:

<system.webServer> 
      <modules> 
        <remove name="UrlRoutingModule-4.0" /> 
        <add name="UrlRoutingModule-4.0" type="System.Web.Routing.UrlRoutingModule" preCondition="" /> 
      </modules> 
    </system.webServer>

After upgrading to Microsoft.AspNet.SignalR 1.0.0-alpha2 NuGet added an ~/App_Start/RegisterHubs.cs, but I didn't think that was working for me due to using Web Forms and my setup. I had to add RouteTable.Routes.MapHubs(); to my Global.asax Application_Start method.

void Application_Start(object sender, EventArgs e)
    {
        RouteTable.Routes.MapHubs();
    }

Basically make sure you can use the new routing features that were added in .Net 3.5 SP1 (System.Web.Routing). Since SignalR depends on them, you will need to ensure that they are working. Try adding a custom route to test that your routing is working.

Adlar answered 3/12, 2012 at 0:38 Comment(1)

This is no longer valid for SignalR v2 – Osseous 7/2, 2019 at 2:32

My fault was the missing Global.asax file in directory (dll is not enough)

Catchall answered 13/8, 2013 at 8:38 Comment(1)

Nice. I just spent an hour trying all other tricks, but this worked – Homicide 13/3, 2014 at 14:50

Old post, but still valuable. If someone tried all above options, make sure you put Microsoft.Owin.Host.SystemWeb.dll library into Bin folder of production server. This library is responsible to create /signalr/hubs folder. There is no direct dependency on this library so may be IIS will not through any error without it that's why we forgot to upload it. Hope this will help.

Kieserite answered 17/5, 2020 at 1:25 Comment(0)

Hot tags

Godot Unity Godot Help Programming Godot 4.X GUI GDScript 3D 2D Physics CSharp Godot 3.X VR XR Projects C++

Recommended topics

Hot tags