I spent some more time with this today and was able to work around it by 
disabling wake-on-lan. Hope that helps track this down!

On Sat, Jan 6, 2024, at 3:50 PM, Brian John wrote:
> Hello! I've been running guacamole for years but just started to have this 
> issue and I'm a little stumped. When I connect to a computer using my web 
> browser, I get a "The connection has been closed because the server is taking 
> too long to respond." error. As far as I can tell, nothing is wrong with the 
> client machines, and it started doing this for all of them at the same time. 
> I would love any help you could provide!
> 
> I have guacamole running in Docker. Looking at the logs, I can see guacd 
> create and remove a connection pretty much instantaneously:
> 
> guacd[1]: INFO: Creating new client for protocol "rdp"
> guacd[1]: INFO: Connection ID is "$8f71f593-2fc4-4a7c-8308-3e32c8e9cf1c"
> guacd[119]: INFO:       Security mode: NLA
> guacd[119]: INFO:       Resize method: none
> guacd[119]: INFO:       No clipboard line-ending normalization specified. 
> Defaulting to preserving the format of all line endings.
> guacd[119]: INFO:       User "@ce073efa-0465-4f9b-936f-877761dffb6e" joined 
> connection "$8f71f593-2fc4-4a7c-8308-3e32c8e9cf1c" (1 users now present)
> guacd[1]: INFO: Connection "$8f71f593-2fc4-4a7c-8308-3e32c8e9cf1c" removed.
> 
> On the guacamole side it tries to connect, then guacd removes the connection, 
> and then 15s later guacamole times out the connection:
> 
> 21:47:46.148 [http-nio-8080-exec-8] INFO  o.a.g.tunnel.TunnelRequestService - 
> User "guacadmin" connected to connection "3".
> 21:48:01.164 [Thread-7] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - 
> Connection to guacd terminated abnormally: Connection to guacd timed out.
> 21:48:01.165 [Thread-7] INFO  o.a.g.tunnel.TunnelRequestService - User 
> "guacadmin" disconnected from connection "3". Duration: 15016 milliseconds
> 21:48:20.803 [http-nio-8080-exec-5] INFO  o.a.g.tunnel.TunnelRequestService - 
> User "guacadmin" connected to connection "3".

Reply via email to