Remotely connect to .net core self hosted web api

Question

I have a simple .net core web api with one action:

[Route("[action]")]
public class APIController : Controller
{
    // GET api/values
    [HttpGet]
    public string Ping()
    {
        return DateTime.Now.ToString();
    }
}

If I run this via dotnet run I get

Hosting environment: Production
Content root path: C:\Users\xxx\Documents\Visual Studio 2015\Projects\SelfHostTest\src\SelfHostTest
Now listening on: http://localhost:5000
Application started. Press Ctrl+C to shut down.

Going to the browser and typing in http://localhost:5000/ping results in a successful return of the current time. However going to a remote machine (same LAN) and trying to access the service via http://odin:5000/ping results in a 404 error. (Odin is the name of the machine running the web api in a console via dotnet run).

Both server (and client!) firewalls are turned off. I can ping "odin" successfully.

Any ideas what simple step I am missing here. I've tried this at home and at work with no success.

What happens if you try with IP address of 'odin'? Ex: 192.111.11.2:5000 ? May be [this](http://stackoverflow.com/questions/12460562/consuming-asp-net-web-api-service-from-other-computer-in-lan) can help you. — Siva Gopal, Sep 27 '16 at 19:06
same thing tried 192.168.1.2 , both on server and on client. 127.0.0.1 works on the server though! — Calanus, Sep 27 '16 at 19:11

Feasoron · Accepted Answer · 2018-02-01T18:37:51.360

90

My guess is that the issue isn't in your controller, it is in program.cs. You need to modify the construction of your WebHost

var host = new WebHostBuilder()
.UseKestrel()
.UseContentRoot(Directory.GetCurrentDirectory())
.UseUrls("http://localhost:5000", "http://odin:5000", "http://192.168.1.2:5000")
.UseIISIntegration()
.UseStartup<Startup>()
.Build();

Unless you add the UseUrls line, Kestrel isn't going to listen outside of localhost. This makes sense, because in a normal situation Kestrel will be sitting behind a reverse proxy like IIS or NGNIX and doesn't need to bind to external URLs.

edited Feb 01 '18 at 18:37

answered Sep 27 '16 at 20:06

Feasoron

3,342
1
22
33

2

Thanks - this works! Guess this sort of config really needs to be in a config file of some sort though... ? – Calanus Sep 27 '16 at 21:07
3

Either that or you can use the special ASPNETCORE_URLS environment variable. I wouldn't want to be listening directly with Kestrel in production, though. It really is best to have it sit behind something else. – Feasoron Sep 27 '16 at 21:11
27

In addition, you can use `.UseUrls("http://*:5000")` instead to accept any incoming requests from port `5000`! – Wingjam Mar 03 '18 at 15:32

score 49 · Answer 2 · edited Nov 01 '20 at 22:35

49

The best way is to adjust the launchSettings.json, which is located inside the Properties folder.

Change

"applicationUrl": "https://localhost:5001"

to

"applicationUrl": "https://0.0.0.0:5001"

This allows the Kestrel Web Server to listen for traffic from all Network Interfaces.

edited Nov 01 '20 at 22:35

Martijn Pieters

963,270
265
3,804
3,187

answered Jan 05 '20 at 18:15

Ernest www.ernestech.com

609
7
6

2

There are two applicationUrl part in asp.net core 3.1 where do I add this part? – Shahriar Rahman Zahin Dec 25 '20 at 23:06
1

You should add this to whichever profile you are using to launch your application. – Luke May 30 '21 at 09:26

score 21 · Answer 3 · answered Mar 03 '18 at 15:26

You can simply do the following to create your WebHost, this will allow remote connections to kestrel.

var host = WebHost.CreateDefaultBuilder(args)
                .UseUrls("http://0.0.0.0:80")
                .UseStartup<Startup>()
                .Build();

After using the following code I still wasn't able to access my API remotely, I had to disable the network adapters created by Docker in the windows control panel (Control Panel\Network and Internet\Network Connections)

In the program.cs file – Alexander Cosman Mar 29 '21 at 12:33 — Alexander Cosman, Mar 29 '21 at 12:33

score 10 · Answer 4 · answered Aug 27 '18 at 03:19

10

In my case (.NET core 2.1) I had to modify the Properties/launchSettings.json file.

Set the applicationUrl to a list of allowed urls separated by semicolons like this

"applicationUrl": "https://localhost:5001;http://odin:5000"

Hope this helps someone out there.

answered Aug 27 '18 at 03:19

Mendy

6,517
4
24
37

1

This worked for me with .net core 3.1. Note that it does NOT work when specifying ip addresses. – Christophe Jan 22 '20 at 14:13

score 3 · Answer 5 · answered Mar 04 '18 at 18:11

Another way to solve this problem is editing "applicationhost.config" file. in project folder -> .vs (Hidden folder) -> config open "applicationhost.config" file. Under sites section, site name="your project name" in Bindings node add another binding and change localhost with your "IP/Domain" on "bindingInformation", like This:

<site name="project_name" id="2">
    <application path="/" applicationPool="Clr4IntegratedAppPool">
     <virtualDirectory path="/" physicalPath="D:\Projects\project_directory" />
    </application>
    <bindings>
     <binding protocol="http" bindingInformation="*:5000:localhost" />
     <binding protocol="http" bindingInformation="*:5000:192.168.1.2" />
     <binding protocol="http" bindingInformation="*:5000:odin" />
    </bindings>
</site>

remember Visual Studio must be run as Administrator.

Yes "Remember Visual Studio must be run as Administrator." und you wont loose hours in stupidity like me. :) — Mottor, Jul 13 '21 at 09:38

score 2 · Answer 6 · answered Aug 31 '21 at 12:39

For us, it also worked (i don't know if that is a new feature of of core 3.1) it that way:

 public static IHostBuilder CreateHostBuilder(string[] args) =>
        Host.CreateDefaultBuilder(args)
            .ConfigureWebHostDefaults(webBuilder =>
            {
                webBuilder.UseKestrel();
                webBuilder.UseIIS();
                webBuilder.UseUrls("http://*:8080");
                webBuilder.UseStartup<Startup>();
            });

this works suspiciously good :) – Dettlaff Oct 29 '21 at 17:13 — Dettlaff, Oct 29 '21 at 17:13

score 0 · Answer 7 · answered Dec 19 '17 at 11:01

There is a more accurate way when there are multi IP addresses available on the local machine. Connect a UDP socket and read its local endpoint:

string localIP;
using (Socket socket = new Socket(AddressFamily.InterNetwork, SocketType.Dgram, 0))
{
    socket.Connect("8.8.8.8", 65530);
    IPEndPoint endPoint = socket.LocalEndPoint as IPEndPoint;
    localIP = endPoint.Address.ToString();
}

Remotely connect to .net core self hosted web api

7 Answers7

Linked