Last post Feb 19, 2014 05:01 PM by skehoe1989
Feb 10, 2014 11:06 AM|skehoe1989|LINK
This is a fairly complex issue, so I will try to go into as much detail as possible. If any addition information would be helpful please let me know and I'll do my best to clarify. I have a Lightswitch HTML application (based on ASP.NET) hosting a SignalR
hub under IIS 7.5 on Windows Server 2008 R2. I plan to deploy the web application on both a sandbox machine, and a production box. The .NET framework is up to date, and the operating systems are fully patched with updates.
Several months ago I set up the web application in the sandbox environment and after a big of trouble in getting it to work the issue turned out to be a .NET version problem (4.5 was needed to support web sockets). Before we came to that conclusion however,
I remember making lots of little tweaks to IIS and the Windows system to try to enable the ASP route (but I didn't think it was the problem since the .NET version requirement ended up being the main issue). Now, several months later, we are trying to deploy
to production and are unable to access the hub at localhost/MyWebApp/SignalR even though the hub appears to be running - leading me to think that maybe one of my little tweaks when I installed it in the Sandbox may have been relevant.
A sample from the IIS logs leads me to believe the hub has started even if it is inaccesible
2013-12-04 22:10:24 ::1 POST /MyWebApp/SignalR/signalr/send transport=serverSentEvents&connectionToken=nG4TV9wqW6Z57xQuDE9s4NSIbiwuODjzietPyBCNj9dLowVlwnDUHOU60MO7hMjxq6tuahrPToHe0_O3icbcaU9L1eBSrU_d1r_ocxHfoJy11nnyBtvd7mfzNZzWJ4Hk0 80 - ::1 SignalR.Client/126.96.36.199+(Microsoft+Windows+NT+6.1.7601+Service+Pack+1)
200 0 0 31
(Seems wierd this post has a 200 response code when im unable to connect to /MyWebApp/SignalR/ and when I navigate to /MyWebApp/SignalR/ in the browser I get a 404, not the expected 500 error for wrong transport.
Since these production machines are configured in a highly secure environment, I was wondering if anything in the environment might be blocking Signalr from hosting its localhost/MyWebApp/SignalR route endpoint. Any suggestions on an approach for going forward
in the debug process, like IIS features to check, different points to log etc would be very much appreciated. Thank you for all the hard work on the SignalR project!
Feb 10, 2014 11:59 PM|Topspy|LINK
Do you manage the production server yourself? Have you tried to check the system event log? If it's not working, it must be recorded there.
Feb 19, 2014 12:46 PM|davidfowl|LINK
How is the application configured on iis? What is the vdir and what do you call when you setup SignalR in Startup.cs.
Feb 19, 2014 04:49 PM|skehoe1989|LINK
Our client manages it, but I can get access to the event viewer logs later this week, I will definitely check it for SignalR related errors! I'm guessing it would appear under Windows > Applications.
Feb 19, 2014 05:01 PM|skehoe1989|LINK
Currently this application still uses version 1.1.3 but the startup code in the Global.asax file is as follows
var config = new Microsoft.AspNet.SignalR.HubConfiguration
EnableCrossDomain = true
Seeing as you're a lead developer on SignalR, if you believe it might solve the problem by upgrading I'd be happy to try early next week. However, this was working in the sandbox environment so id be very suprised if it wasnt an environmental or IIS configuration
problem. I will be sure to post even viewer info once I can get back on the machine.