Hello ivanmarcus and thanks for your reply.
I have already check the page you have link to me and my configurations
looking exactly the same as described on that page.

I think my issue is here on nginx.conf:

location / {
    proxy_pass http://*HOSTNAME*:8080/guacamole/;
    proxy_buffering off;
    proxy_http_version 1.1;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_cookie_path /guacamole/ /;
    access_log off;
}

after lots of try, I have see that if I change *HOSTNAME* and I set my local
IP (such 10.10.0.1 i.e.) than in Guacamole I get 10.10.0.1 for IP, if I set
127.0.0.1 or localhost I get 127.0.0.1 (or, randomly, 0:0:0:0:0:0:0:1), if i
set my public IP or my FQDN than I get a 504 from nginx (I do not have
forwarder port 8080 to my servlet container, so I can't login directly from
remote).

Tomcat side is look like this (I have omitted the rest of configuration just
because Tomcat work both from local connection and remote connection):

*<Valve className="org.apache.catalina.valves.RemoteIpValve"
    internalProxies="127.0.0.1"
    remoteIpHeader="x-forwarded-for"
    remoteIpProxiesHeader="x-forwarded-by"
    protocolHeader="x-forwarded-proto" />*

plus I have set also a Valve for access log, here my conf:

*<Valve className="org.apache.catalina.valves.AccessLogValve"
    directory="logs"
    prefix="localhost_access_log"
    suffix=".txt"
    pattern="%a Remote User[ %{X-Forwarded-For}i %l %u %t ] Request[ %r ]
Status Code[ %s ] Bytes[ %b ] Referer[ %{Referer}i ] Agent[ %{User-agent}i
]" />*

On every changes I had done both on Tomcat and/or NGINX I had always restart
daemons.

I'm hitting my head on the wall, where I'm wrong? Please help! 

Thanks, Alessandro.



--
Sent from: 
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to