[
https://issues.apache.org/jira/browse/GUACAMOLE-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-2107:
-------------------------------------
Affects Version/s: (was: 1.5.4)
(was: 1.5.5)
> WOL (Wake On LAN) feature doesn't work on version newer than 1.5.4
> ------------------------------------------------------------------
>
> Key: GUACAMOLE-2107
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-2107
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole, guacd
> Affects Versions: 1.6.0
> Environment: Docker 28.1.1 on x86 or ARM
> Reporter: Lorenzo S.
> Priority: Minor
> Attachments: Screenshot 2025-07-26 at 6.04.26.png, Screenshot
> 2025-07-26 at 6.12.56.png, Screenshot 2025-07-26 at 6.13.11.png
>
>
> Hello,
> I have confirmed that on guacamole version newer than 1.5.3 the WOL feature
> is not working. Specifically the WOL packet is not sent, and the connection
> times out after 10s despite to have set a longer time (screenshot attached).
> Checking the logs "guacd" provided the below messages:
>
> {code:java}
> guacd[1]: INFO: Creating new client for protocol "rdp"
> guacd[1]: INFO: Connection ID is "$f41f9319-154b-4c58-9b9c-3d9fd6995046"
> guacd[16]: INFO: Security mode: Negotiate (ANY)
> guacd[16]: INFO: Resize method: display-update
> guacd[16]: INFO: Clipboard line ending normalization: Preserve (none)
> guacd[16]: INFO: User "@6ec7067c-b91e-43b3-80b0-2fbeb9d7bb36" joined
> connection "$f41f9319-154b-4c58-9b9c-3d9fd6995046" (1 users now present)
> guacd[16]: INFO: Local system reports 4 processor(s) are available.
> guacd[16]: INFO: Graphical updates will be encoded using 4 worker
> thread(s).
> guacd[16]: INFO: Loading keymap "base"
> guacd[16]: INFO: Loading keymap "ja-jp-qwerty"
> guacd[16]: WARNING: Ignoring requested color depth of 16 bpp, as the RDP
> Graphics Pipeline requires 32 bpp.
> guacd[16]: INFO: RDP server closed/refused connection: Server refused
> connection (wrong security type?)
> guacd[16]: INFO: User "@6ec7067c-b91e-43b3-80b0-2fbeb9d7bb36"
> disconnected (0 users remain)
> guacd[16]: INFO: Last user of connection
> "$f41f9319-154b-4c58-9b9c-3d9fd6995046" disconnected
> guacd[1]: INFO: Connection "$f41f9319-154b-4c58-9b9c-3d9fd6995046"
> removed. {code}
> and "guacamole" this one:
> {code:java}
> 21:03:32.450 [http-nio-8080-exec-8] INFO o.a.g.event.EventLoggingListener -
> User "*****" (authenticated by "postgresql") successfully authenticated from
> 192.168.10.156
> 21:04:12.231 [http-nio-8080-exec-7] INFO o.a.g.tunnel.TunnelRequestService -
> User "*****" connected to connection "11".
> Exception in thread "Thread-2" java.lang.IllegalStateException: Message will
> not be sent because the WebSocket session has been closed
> at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:454)
> at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlockInternal(WsRemoteEndpointImplBase.java:312)
> at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:265)
> at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:249)
> at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:191)
> at
> org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:36)
> at
> org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint.sendInstruction(GuacamoleWebSocketTunnelEndpoint.java:152)
> at
> org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint.access$200(GuacamoleWebSocketTunnelEndpoint.java:53)
> at
> org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint$2.run(GuacamoleWebSocketTunnelEndpoint.java:253)
> 21:04:21.370 [http-nio-8080-exec-8] INFO o.a.g.tunnel.TunnelRequestService -
> User "*****" disconnected from connection "11". Duration: 9124 milliseconds
> {code}
> It does show an issue with "Websocket" but it's not related as I am not using
> a Proxy and without using WOL it works with no issues.
>
> The workaround is using version 1.5.4 (for the supported architecture).
> Regards
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
