Self hosted OWIN and urlacl

Question

I've created a self hosted Nancy/SignalR application self-hosted in OWIN using Microsoft.Owin.Host.HttpListener and Microsoft.Owin.Hosting

Things work perfectly fine locally but as soon as I try to use anything but localhost to access the app I get a HTTP Error 503. The service is unavailable error. I can't even access the app using 127.0.0.1 or the machine name.

I've tried adding the port to urlacl using

http add urlacl http://*:8989/ user=EVERYONE but doesn't seem to do anything.

here are the OWIN start options that I've tried,

        var options = new StartOptions
        {
            Url = "127.0.0.1",
            App = GetType().AssemblyQualifiedName,
            Port = _configFileProvider.Port
        };

    var options = new StartOptions
        {
            App = GetType().AssemblyQualifiedName,
            Port = _configFileProvider.Port
        };

here is the source code for the file that starts and stops the server https://github.com/NzbDrone/NzbDrone/blob/vnext/NzbDrone/Owin/OwinHostController.cs

Try changing Url to "*" instead of binding to 127.0.0.1 only. — davidfowl, May 20 '13 at 05:13

kay.one · Accepted Answer · 2013-10-02T20:06:34.953

28

so it turns out you need to pass in a url into StartOptions in the same format as the urlacl.

Changing the start options to the code below fixed the problem. now the app is accessible across the network.

  var options = new StartOptions("http://*:8989")
  {
      ServerFactory = "Microsoft.Owin.Host.HttpListener"
  };

edited Oct 02 '13 at 20:06

answered May 21 '13 at 02:53

kay.one

7,374
6
50
72

1

How does this need to be adapted for SignalR 2 beta? Url and App are not properties of StartOptions as it shows for me. – Jason Kleban Aug 08 '13 at 14:39
@uosɐſupdated sample code to match the syntax for current version of owin (1.1.0 beta 2) – kay.one Oct 02 '13 at 20:07
Wow. Very very useful :) So many other similar answers out there (mostly talking about IIS Express) but this one actually works. – Jedidja Aug 20 '14 at 14:17
1

And, actually, you don't want to reserve ports with urlacl. http://stackoverflow.com/questions/22293445/http-503-service-is-unavailable-when-trying-to-browse-signalr-hubs has some more information. – Jedidja Aug 20 '14 at 14:58
3

In the end, what worked for me on Server 2012 and Windows 8.1 was to use http://+:9000 (with no urlacls set) and have the port open (on the domain in my case). – Jedidja Aug 20 '14 at 14:59
I've been working on this for the past two days and I was so frustrated I wanted to stab a puppy. thank you! – viggity May 15 '15 at 15:25

score 12 · Answer 2 · answered Aug 12 '14 at 13:21

I spend many hours solving similar issue on Windows 8.1.

    StartOptions options = new StartOptions();

    options.Urls.Add("http://localhost:9000");
    options.Urls.Add("http://127.0.0.1:9000");
    options.Urls.Add("http://192.168.0.102:9000");
    options.Urls.Add(string.Format("http://{0}:9000", Environment.MachineName));

    WebApp.Start<Startup>(options);

I could not listen or was getting 503 error...

If you want to listen on several IP addresses, each address needs its own urlacl record:

Does NOT work:

    netsh http>add urlacl http://+:9000/ user=EveryOne

OK:

    netsh http>add urlacl http://localhost:9000/ user=EveryOne
    netsh http>add urlacl http://127.0.0.1:9000/ user=EveryOne
    etc.

After adding reservation for each address individually, everything works fine.

Adding several IP addresses or URL's also works with new StartOption("http://*:9000/") on Microsoft.Owin.Hosting 3.0.1. and netsh http> add urlacl http://*:9000/, or run your app as admin. — flip, Aug 12 '15 at 18:54

score 9 · Answer 3 · answered Jun 07 '16 at 15:28

Thanks to the info that @kay.one provided I was able to access my self-hosted Web API 2.2 (OWIN/Katana, console app) from the same machine via IP address. However just consolidate it into a simple step-by-step:

In Main of Program.cs (for console app): WebApp.Start<Startup>("http://*:8080");
From Windows Command Prompt (run as Administrator) enter netsh http add urlacl http://*:8080/ user=EVERYONE
Go to Windows Firewall with Advanced Security and add an Inbound Rule that opens up TCP port 8080

You should then be able to access from another machine using IP address or computer name.

Disclaimer: I'm not a security expert so I don't know the security implications of doing this.

Self hosted OWIN and urlacl

3 Answers3

Linked

Related