When a user is signed into the forum under an IPV6 address their IP shows up as 127.0.0.1 in the administrator panel. [nqJowSB] This is using the latest version.

[image] Gulshan_Kumar: I couldn’t try successfully above method. Site appears down. same effect here. How did you solve the problem?

Hey @adorfer I fixed this problem by keeping only A record with IPV4 address, and removing AAAA record which had IPV6 address.

“disabling ipv6/AAAA on the forum”: That’s no option here for us. Any other suggestions what i can check/try/test?

Check Discourse with jwilder/nginx-proxy howtos? - #6 by vitorl for an example of how to set set_real_ip_from.

I understand: i have to put manally an nginx as reverse proxy in front of discourse? (So it’s not feasable by “discourse itself”?)

No. You add to the app.yml to have those changes made inside the container. Edit: See section that says [image]Discourse with jwilder/nginx-proxy howtos? To fix discourse not getting the real IP from the host nginx, add this to your app.yml : I think you want to add something like set_real_ip_from YOUR_IPV6;

But for that i need at least the initial statement for an nginx proxy to be installed in the system as multi server loadbalancing setup (as i understand the howto above) or in other words: i no even have the stuff “to replace in the app.yaml”. perhaps i should look for some kind of “more complex installation”. currently my system was just running simple. for the moment there is no such thing “replace:” in my app.yml [image] pfaffman: run: - replace: filename: /etc/nginx/conf.d/discourse.conf from: “types {” to: | set_real_ip_from 172.18.0.0/24; real_ip_header X-Forwarded-For; real_ip_recursive on; types { in plus it’s unclear for me is what this syntax “set_real_ip_from YOUR_IPV6;” would be in reality. For a parameter i miss something like a “$variable” or “”, in plus the format is unclear: with netmask or is an /128 fixed? (in other words: a real world example would be really helpful)

Just in order to bump this thread: Does anybody haven an idea what i could try out or test? I have 3 different Discourse-Installations, on different machines and different ubuntu-versions (just for notice), with IPv6 enabled, and on all of them it’s the same: IPv6-users are reported with an RFC1918-IPv4 (probably from the docker-bridge) in the logs.

Sadly the same for me. Installing without Docker results in broken IPv6 (Welcome to nginx), with Docker results in the named error. IPv6 would need to be redone without NAT, if you don’t have any idea for a workarround.

I’ve just noticed that the IP addresses for a lot of members on my forum are being stored as 172.17.0.1. I’m not running a reverse proxy or anything - there’s nothing between you and Discourse’s Docker. Any ideas?

Remote users IPV6 address shows as localhost

Product Support

pfaffman (Jay Pfaffman) August 25, 2020, 12:51am 24

See Last IP address and action_dispatch.trusted_proxies - #3 by mpalmer

Topic		Replies	Views
IPv6 hides Users real IP Product Support	0	88	March 31, 2025
Inconsistent / missing registration & last IP Product Support	13	1646	August 10, 2019
Discourse shows server IP/localhost as user's IP Self-hosting unsupported-install	18	2580	July 12, 2022
Using IPv6 NAT function in Docker with Discourse Self-hosting	4	995	April 5, 2023
IP address of users showing as server IP Self-hosting	4	1522	January 23, 2020

Remote users IPV6 address shows as localhost

Related topics