On Mon, Jun 21, 2021 at 3:05 AM Martin Krellmann <[email protected]> wrote:
> Hello Guacamole community. > > > > I have a strange problem regarding WebSocket Support: While the log claims > it is loaded there is simply no “/guacamole/websocket-tunnel” endpoint > available. I have checked this several times directly from the CLI of the > docker container. It returns a 404. > The endpoint is definitely available. You are seeing a 404 because it is a WebSocket endpoint, not an HTTP endpoint, and Tomcat is refusing to continue routing the request without the correct headers. You would need to use a WebSocket client to attempt to connect to the WebSocket tunnel endpoint. Since if have installed guacamole via the Univention appcenter in the first > place, I have updated it now to the latest docker images available. The > problem remains. > Can you share what problem you're referring to? However, the configuration still uses the LDAP Backend of univention. Which > works fine for the HTTP tunnel, but as no websocket-tunnel endpoint is > provided in Tomcat it couldn’t use it. To clarify again… This is not a > reverse proxy issue. The endpoint is already not available in tomcat > (checked from the CLI). > If the HTTP tunnel works fine but WebSocket fails, that definitely sounds like a reverse proxy issue. You can confirm this further by connecting directly to Tomcat with a browser rather than through the reverse proxy, but really the WebSocket tunnel is there. - Mike
