10

I try to get remote (client) IP addres:

var ip = httpContext.Features.Get<IHttpConnectionFeature>()?.RemoteIpAddress

But it works only for local requests (it will return ::1 value)

When I load page from remote machine the value is null. I investigated there is no IHttpConnectionFeature in the Features collection in this case.

Why? And how to get remote ip address correctly?

2
  • 1
    There are several issues with it as far as I know, especially if you host it behind a loadbalancer and/or iis. There is a UseOverrideHeaders or so but will be renamed to UseForwardedHeaders in rc2, see the announcement github.com/aspnet/Announcements/issues/147. But as far as I understand, this may not help you neither, because it returns the last X-Forwarded-For which in many cloud deployments would be the reverseproxy and not the original user. Commented Apr 1, 2016 at 11:29
  • But there is a feature in discussion as far as I know to allow to determine from which hop to get the X-Forwarded-For (i.e. 2 hops back rather than just the latest Commented Apr 1, 2016 at 11:29

2 Answers 2

26

On project.json add dependency:

"Microsoft.AspNetCore.HttpOverrides": "1.0.0"

On Startup.cs, in the Configure method add:

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

And, of course:

using Microsoft.AspNetCore.HttpOverrides;

Then, I got the ip like this:

Request.HttpContext.Connection.RemoteIpAddress

In my case, when debugging in VS I got always IpV6 localhost, but when deployed on an IIS I got always the remote IP.

Some useful links: How do I get client IP address in ASP.NET Core? and RemoteIpAddress is always null

The ::1 may be because:

Connections termination at IIS, which then forwards to Kestrel, the v.next web server, so connections to the web server are indeed from localhost. (https://stackoverflow.com/a/35442401/5326387)

Sign up to request clarification or add additional context in comments.

5 Comments

when you find similar questions, and post similar answers, you might want to add a cross-reference between the two. Especially if one seems more complete than the other. HTH
@superjos what do you mean?
There's another SO question here which is very close to this one and where you basically copied the same answer. It might be useful in such cases to point one question to another. Maybe even flag question for closing.
Yes, the answer is the same because I answered both questions. I was looking for the same and when i found the solution, I answered both questions (i didn't mark as duplicated because both where asked a time ago and both already had different answeres that didn't solve the problem)
This also helps when using ngrok. WIthout this, the RemoteAddress is always ::1.
4

Just try this:

var ipAddress = HttpContext.Connection.RemoteIpAddress;

And if you have another computer in same LAN, try to connect with this pc but use user ip instead of localhost. Otherwise you will get always ::1 result.

1 Comment

Thanks man, I was wondering why it always show ::1 result, and your remark helped me to troubleshoot the problem. Cheeeers =]

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.