[
https://issues.apache.org/jira/browse/GUACAMOLE-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815325#comment-17815325
]
Marcus Kindermann commented on GUACAMOLE-1922:
----------------------------------------------
Hi Nick,
thanks for your fast reply.
Nginx config was correct, but the RemoteIpValve Section was missing in Tomcat
config. However it didn't work with the attributes described in the
documentation. It works for me with the following parameters:
{code:java}
internalProxies="127\.0\.0\.1"
remoteIpHeader="x-forwarded-for"
proxiesHeader="x-forwarded-by"
protocolHeader="x-forwarded-proto" /> {code}
I had to escape the dots in the internalProxies IP address and I had to change
"remoteIpProxiesHeader" to "proxiesHeader" as decribed in the Tomcat
documentation.
[https://tomcat.apache.org/tomcat-10.1-doc/config/valve.html#Remote_IP_Valve]
This works for me, so I don't know if the attributes described in the Guacamole
documentation are still valid for others.
> Remote Host in Active Sessions shows 127.0.0.1
> ----------------------------------------------
>
> Key: GUACAMOLE-1922
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1922
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
> Affects Versions: 1.5.4
> Reporter: Marcus Kindermann
> Priority: Minor
> Attachments: image-2024-02-07-08-45-54-882.png
>
>
> Hi,
> in the Active Sessions Tab in the column 'Remote Host' it shows '127.0.0.1'
> or '0:0:0:0:0:0:0:1' instead of the actual remote hostname or IP. The same
> applies to the 'History' Tab
> !image-2024-02-07-08-45-54-882.png!
> Our Setup: Guacamole 1.5.4 on RHEL8 Server with LDAP auth and PostgreSQL DB
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
