Hello, I just updated to version 1.5.3 (from 1.4.0), and the problem is still the same.
I see the internal Docker IP in the session log :-( How can I fix this? The JIRA ticket is closed: https://issues.apache.org/jira/browse/GUACAMOLE-1005 I don't think it's resolved. čt 18. 3. 2021 v 8:37 odesílatel fed <[email protected]> napsal: > Hi, > > I had the same problem and In some way I managed to make this work mapping > the server.xml file to a local server.xml file after copying the one that > is the default in the docker image to the host. > > So on volumes of guac I have: > - ${PWD}/tomcat_conf/server.xml:/usr/local/tomcat/conf/server.xml > > And this new server.xml is the original one with this section added: > > <Valve className="org.apache.catalina.valves.RemoteIpValve" > internalProxies="172.31.0.1" > remoteIpHeader="x-forwarded-for" > remoteIpProxiesHeader="x-forwarded-by" > protocolHeader="x-forwarded-proto" /> > > It's not a good solution because as you see it depends on the host ip and > this is written in the file and the subnet can change. So to try to avoid > this I created a docker subnet just for guacamole. > > Bye > > On Wed, 17 Mar 2021 at 19:05, Nick Couchman <[email protected]> wrote: > >> On Mon, Mar 15, 2021 at 4:56 AM Martin Vancl <[email protected]> >> wrote: >> >>> Hi, >>> I'm using Guacamole 1.3.0 with docker and nginx ssl proxy. >>> At page https://rdp.example.net/#/settings/postgresql/history all >>> users have the same remote host address "172.18.0.1". It is probably >>> from the docker network. >>> Is possible to have real user IP address at history page? >>> >>> >> You'll need to modify the Tomcat server.xml file within the guacamole >> Docker container and set up the RemoteIp Valve: >> >> >> http://guacamole.apache.org/doc/gug/proxying-guacamole.html#tomcat-remote-ip >> >> -Nick >> > -- S pozdravem Ing. Martin Vancl e-mail: [email protected] web: www.vancl-it.cz
