This appears to have started recently - if you go to a user’s profile > admin - their last IP address is shown as prefixed with ::ffff: (and so when you do an ip lookup it does not work).
No repro here on meta.
Could this be related:
I did add a record to allow IPv6 recently, so could that be it? Do you have IPv6 enabled here?
This (meta) is running on AWS as a dogfooding experiment, so it is possible it is not, because as I understand it AWS doesn’t use ipv6 at all… but we’d need to ask @mpalmer
Meta is now fully IPv6 compatible.
Nice! Were you getting the ::ffff: problem too?
Sorry only just coming back to this. Yes I use HAProxy on the front ![]()
Do I need to do anything special on the Discourse side to enable IPV6?
On the HAProxy side I believe I have changed everything I need to, specifically:
bind *:80
to
bind :::80 v4v6
and
bind *:443 ssl crt /etc/haproxy/certs/
to
bind :::443 v4v6 ssl crt /etc/haproxy/certs/
On http://ready.chair6.net everything passes except for:
IPv6 Connectivity - FAIL - Could not connect (to site) on port 443 over IPv6.
Any idea what I might be missing?
Try instead using two lines as follows:
bind *:80
bind :::80
bind *:443 ssl crt /etc/haproxy/certs/
bind :::443 ssl crt /etc/haproxy/certs/
Hi Michael, updated to:
#bind *:80
#bind :::80 v4v6
#bind *:443 ssl crt /etc/haproxy/certs/
#bind :::443 v4v6 ssl crt /etc/haproxy/certs/
bind *:80
bind :::80
bind *:443 ssl crt /etc/haproxy/certs/
bind :::443 ssl crt /etc/haproxy/certs/
But I’m still getting the same thing. Here’s the full report in case it helps.
fe80::6e62:6dff:fe46:abf9 is a link-local address, only intended to be used by a machine on the same broadcast domain as the server. Nothing else on the Internet will ever be able to connect to it.
Does the server have a “real” IPv6 address (such as something starting with a 2)?
太棒了,已修复!(我需要将服务器从 IPv6 发现 改为 静态配置,并手动添加范围。)
感谢您的帮助 ![]()

