RemoteIpAddress is always null

Question

var test1 = HttpContext.Features.Get<IHttpConnectionFeature>();
var test2 = HttpContext.Connection.RemoteIpAddress;

When running the application locally on IISExpress, these two lines correctly return the value 0:0:1.

When I publish the application on IIS 7.5 (which is running on a VM). RemoteIpAddress is always null

I am using ASP.Net 5 RC 1.

How can I get the client's IP address in an ASP.NET 5 application ?

I tried the solutions in the following questions, however I have the problem mentioned above:

The X-Forwarded-For appears to be set by default in RC1 U1 from this [Answer](http://stackoverflow.com/a/36316189/538763) — crokusek, Mar 30 '16 at 17:57

score 13 · Answer 1 · answered Feb 16 '16 at 20:30

13

What you're seeing is accurate, if not useful. Connections termination at IIS, which then forwards to Kestrel, the v.next web server, so connections to the web server are indeed from localhost.

What you need to do is enable support for X-Forwarded-For

Add the Microsoft.AspNet.HttpOverrides package

In your Configure() method add

    app.UseOverrideHeaders(new OverrideHeaderMiddlewareOptions
    {
        ForwardedOptions = ForwardedHeaders.XForwardedFor | 
                           ForwardedHeaders.XForwardedProto
    });

Note that this package will change in RC2 to make it safer to use.

answered Feb 16 '16 at 20:30

blowdart

55,577
12
114
149

1

Still getting null. Apparently this is due to a bug: https://github.com/aspnet/IISIntegration/issues/17#issuecomment-184855218 – A-Sharabiani Feb 16 '16 at 20:47
Ah darn. Move to IIS8? *grin* – blowdart Feb 16 '16 at 23:52
14

The nuget package is now **Microsoft.AspNetCore.HttpOverrides** and the configure method is: **app.UseForwardedHeaders(...)** – CB-Dan Aug 12 '16 at 22:07

score 10 · Answer 2 · answered Nov 20 '17 at 13:29

In ASP.NET Core 2.0 project you need to add package Microsoft.AspNetCore.HttpOverrides and add this code to your Configure method:

app.UseForwardedHeaders(new ForwardedHeadersOptions
{
    ForwardedHeaders = ForwardedHeaders.XForwardedFor | ForwardedHeaders.XForwardedProto
});

score 2 · Answer 3 · answered Apr 02 '19 at 12:43

2

That is because of you are trying to connect from localhost. If you have another computer in same LAN, try to connect with this pc but use user ip instead of localhost.

answered Apr 02 '19 at 12:43

Emre SOLUĞAN

193
1
12

RemoteIpAddress is always null

3 Answers3

Linked