SignalR Hub on IIS
Closed this issue · 7 comments
Hi,
it's me again, i am using your angular signalr hub a couple of weeks and so far everything
worked fine but now i ran into a problem, maybe it's a general signalR roblem or a config thing, i don't know right now.
I was hosting my testapp on the ASP development Server where everyting worked fine, now i was trying to host it on my local IIS 8.5 and it's not working anymore. I receive an error while starting the hub ("Error during negotiation request -> Page not Found 404"), therefore i have also tested your sample Grid on my local IIS and i received the same error. Any ideas what i am doing wrong, i read a lot about crossdomain access and stuff like that, but i dont think that this is the problem.
Kind Regards
Manuel
Interesting. I actually have a web app that is using SignalR and running in IIS 8.5 on Win Server 2012 and I can't seem to reproduce this problem. The error makes it sound like SignalR isn't running correctly and binding /signalr on the server. I would suggest posting this question to SignalR
Hi Justin,
I solved my problem, it turned out that everything works fine with version 1.1.1 of the angularjs hub from your demogrid project and setting the rootPath.
If I do the same with the current nuget package which is version 1.3.3 it does not work.
Just wanna let you know.
From: Justin Maier [mailto:notifications@github.com]
Sent: Dienstag, 11. November 2014 18:27
To: JustMaier/angular-signalr-hub
Cc: blenet
Subject: Re: [angular-signalr-hub] SignalR Hub on IIS (#20)
Interesting. I actually have a web app that is using SignalR and running in IIS 8.5 on Win Server 2012 and I can't seem to reproduce this problem. The error makes it sound like SignalR isn't running correctly and binding /signalr on the server. I would suggest posting this question to SignalR https://github.com/SignalR/SignalR
—
Reply to this email directly or view it on GitHub #20 (comment) . https://github.com/notifications/beacon/AI0kY3-1cStmIkkZ-Iyx6JpcPcQvtuXkks5nMj5wgaJpZM4C5sC9.gif
Glad to hear that you got your issue resolved. I'm going to leave this open for now to see if anyone else has anything to report here.
Sorry I did not understand what is the working version and where can I find it?
I'm curious if there's been any headway on this issue. I'm running into the same thing on Angular 1.3.10.
Everything seems to work fine if you're debugging inside VisualStudio (2012 and 2013), but the moment it is deployed to an actual IIS - whether localhost or remote - this issue crops up. According to my browser dev tools, under the networking tab, there seems to be looking for http://localhost/signalr (or https://[deployedServer.com]/signalr if deployed to a remote server) and not finding it.
I guess it doesn't come up in VS because VS launches the debugged application at the root of it's virtual web server. But why is it looking for such a folder at the root of the server, instead of inside the application folder itself? And more importantly, how can we work around this?
I just realized I forgot to update my solution. After taking another look at your documentation, I saw the rootpath attribute in the hub factory, and was able to set that to my desired path of the signalr folder. Thank you for adding that attribute to your wrapper!!!
I've successfully launched an application with angular 1.3.10 and your library on windows server 2012 running iis 8.5. Given the rootpath attribute is in place to handle just this type of situation, I'd consider this issue closed.
Glad to hear that you were able to figure this out. Sorry I wasn't present to lend a helping hand.