search

boschkundendienst / guacamole-docker-compose

Guacamole with docker-compose using PostgreSQL, nginx with SSL (self-signed)
GNU General Public License v3.0
983 stars 410 forks source link

HTTP-Fallback not working properly #93

Closed bernhardsteindl closed 4 months ago

bernhardsteindl commented 5 months ago

Hi,

thank you for your project. I've tried native guacamole and this docker-compose-project - but sadly here the HTTP-Fallback isn't working properly. See the logs below:

guacamole_compose           | 07:58:35.170 [http-nio-8080-exec-6] INFO  o.a.g.r.auth.AuthenticationService - User "user" successfully authenticated from <IP-Adress>.
guacamole_compose           | 07:58:43.055 [http-nio-8080-exec-2] INFO  o.a.g.tunnel.TunnelRequestService - User "user" connected to connection "8".
guacamole_compose           | 08:02:21.617 [http-nio-8080-exec-7] INFO  o.a.g.tunnel.TunnelRequestService - User "user" connected to connection "4".
guacamole_compose           | 08:02:21.617 [http-nio-8080-exec-7] INFO  o.a.g.t.h.RestrictedGuacamoleHTTPTunnelServlet - Using HTTP tunnel (not WebSocket). Performance may be sub-optimal.
guacamole_compose           | 08:03:02.124 [http-nio-8080-exec-4] INFO  o.a.g.tunnel.TunnelRequestService - User "user" connected to connection "4".
guacamole_compose           | 08:03:02.125 [http-nio-8080-exec-4] INFO  o.a.g.t.h.RestrictedGuacamoleHTTPTunnelServlet - Using HTTP tunnel (not WebSocket). Performance may be sub-optimal.
guacamole_compose           | 08:03:15.601 [http-nio-8080-exec-11] INFO  o.a.g.tunnel.TunnelRequestService - User "user" disconnected from connection "4". Duration: 53984 milliseconds
guacamole_compose           | 08:03:15.605 [http-nio-8080-exec-11] ERROR o.a.g.s.GuacamoleHTTPTunnelServlet - HTTP tunnel request failed: Connection to guacd timed out.
guacamole_compose           | 08:03:15.650 [http-nio-8080-exec-3] WARN  o.a.g.s.GuacamoleHTTPTunnelServlet - HTTP tunnel request rejected: No such tunnel.
guacamole_compose           | 08:03:15.652 [http-nio-8080-exec-3] WARN  o.a.g.s.GuacamoleHTTPTunnelServlet - HTTP tunnel request rejected: No such tunnel.
guacamole_compose           | 08:06:14.998 [pool-3-thread-1] INFO  o.a.g.tunnel.TunnelRequestService - User "user" disconnected from connection "4". Duration: 192873 milliseconds
guacamole_compose           | 08:06:15.000 [http-nio-8080-exec-5] INFO  o.a.g.tunnel.TunnelRequestService - User "user" disconnected from connection "4". Duration: 192875 milliseconds
guacamole_compose           | 08:06:21.417 [http-nio-8080-exec-9] INFO  o.a.g.tunnel.TunnelRequestService - User "user" connected to connection "4".
guacamole_compose           | 08:06:21.418 [http-nio-8080-exec-9] INFO  o.a.g.t.h.RestrictedGuacamoleHTTPTunnelServlet - Using HTTP tunnel (not WebSocket). Performance may be sub-optimal.
guacamole_compose           | 08:07:59.998 [pool-3-thread-1] INFO  o.a.g.tunnel.TunnelRequestService - User "user" disconnected from connection "4". Duration: 98580 milliseconds
guacamole_compose           | 08:07:59.999 [http-nio-8080-exec-10] INFO  o.a.g.tunnel.TunnelRequestService - User "user" disconnected from connection "4". Duration: 98581 milliseconds

I've no idea why this isn't working but I think it relies on the configuration up here.

boschkundendienst commented 5 months ago

If you use http and directly connect to guacamole (without nginx) the URL must end with /guacamole so for example:

https://yourserver:8080/guacamole

If running with nginx on https nginx will redirect to /guacamole automatically, I think, that is the missing piece here.