On Thu, Sep 18, 2025 at 11:44 PM Guacamole <[email protected]> wrote:
> I am running the latest Guacamole Docker image behind a reverse proxy > (Pangolin stack) that correctly sets the X-Forwarded-For header. Whether > I configure the RemoteIpValve via an environment variable in > docker-compose.yml or via a valve definition in server.xml, it works as > expected in the Guacamole web UI, where, for example, the client's public > IP is displayed correctly in the 'Active Sessions' UI. But the Tomcat > access log (using LogbackAccessValve) only logs the proxy's internal IP. > Why is the application seeing the correct IP while the access log is not? > > Hello, Dave, This sounds like more of a Tomcat issue than a Guacamole issue, so you might have better success asking this question on the Tomcat mailing list. I did come across the following information with a quick Internet search: https://stackoverflow.com/questions/48103673/how-to-log-client-ip-and-x-forwarded-for-ip-in-tomcat-access-log#48180469 https://codingtechroom.com/question/how-to-log-client-ip-and-x-forwarded-for-ip-in-tomcat-access-log -Nick >
