SignalR Self-Service Deployment

Question

I created a couple of C # console applications based on this SignalR Console sample application .

This works fine on my local PC, and now I copied the server application (plus all the files from the bin / Release folder) to my server. When I launch the server application, he joyfully sits there, listening to " http://www.redacted.com:8088/ ".

In the client application, I changed:

var _connection = new HubConnection("http://127.0.0.1:8088/"); 

in

 var _connection = new HubConnection("http://www.redacted.com:8088/"); 

However, now I get a 503 Server Unavailable error message when I try to start a connection. I am new to SignalR and could not find a decent tutorial on deployment (mainly because there are probably many ways that can be accomplished depending on the requirements I assume).

So my questions are:

• Do I need to configure something in IIS for this to work (bearing in mind that I don’t look at what this web application is, just a console application for a console application), or is it normal, just start the exe server and open the port up?

• My server is running Windows Server 2012, and I added my exe to the list of applications that are allowed to create connections and added an incoming rule for port 8088, is there anything else I need to do to be visible to my client?

Answer 1

If you have something along these lines on the server

  string url = "http://127.0.0.1:8088/"; var server = new Server(url); server.MapHubs(); server.Start(); 

Try binding to all IP addresses (or hosts)

  string url = "http://*:8088/";