Hello, I am facing the same issue. Could you please provide the exact steps to log the ACTUAL IP of the user?
Thanks a ton! Prakhar ________________________________ From: Maciej Konigsman <[email protected]> Sent: Wednesday, October 25, 2023 18:21 To: [email protected] <[email protected]> Subject: Re: Bad user remote IP Thanks for your help. It works with the following internalProxies="127\.\d+\.\d+\.\d+|10\.\d+\.\d+\.\d+" 127... - for nginx running on the same server as Guacamole 10... - AWS private network On Wed, 25 Oct 2023 at 13:25, Henri Alves de Godoy <[email protected]<mailto:[email protected]>> wrote: Hi all, the remote ip registration only worked when I put the options below in server.xml ------- <Valve className="org.apache.catalina.valves.RemoteIpValve" internalProxies="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1" remoteIpHeader="x-forwarded-for" remoteIpProxiesHeader="x-forwarded-by" protocolHeader="x-forwarded-proto" /> <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log." suffix=".txt" pattern="combined" requestAttributesEnabled="true" /> ---------- Att, Henri. Em qua., 25 de out. de 2023 às 08:16, Nick Couchman <[email protected]<mailto:[email protected]>> escreveu: On Wed, Oct 25, 2023 at 6:19 AM Maciej Konigsman <[email protected]> wrote: Valve config <Valve className="org.apache.catalina.valves.RemoteIpValve" internalProxies="127.0.0.1" remoteIpHeader="x-forwarded-for" remoteIpProxiesHeader="x-forwarded-by" protocolHeader="x-forwarded-proto" /> What private subnet applies to your ELB? ELB is in the same subnet as the EC2 instance where Guacamole is installed. Presumably the ELB is not running on the localhost (127.0.0.1), so I suspect that you need the actual IP address(es) and/or subnets of the ELB placed into the "internalProxies" property in this valve. -Nick -- [https://ci3.googleusercontent.com/mail-sig/AIorK4xJTI4fOwTRhNqwzPDuuVtXRma-AtZlVMXEBX8smzlKDm1b6O7MmBLRqUMlR7HmEqRCaiKlXCY]
