Yeah, still happening
To everyone’s knowledge, should a dropped-in real_ip_header X-Forwarded-For;
in the discourse {} block of the container’s nginx/conf.d/discourse.conf
suffice for IP forwarding, and therefore might something else be going wrong if that’s not working? And is it strange that the discourse app has been able to detect requester IPs (e.g. for banning purposes) in the past with these same configs, if the container’s /var/log/nginx/access.log
definitely can’t tell them apart now, no matter where I insert that config line?