On Wed, Mar 31, 2021 at 2:34 PM Alexandre Almosni < [email protected]> wrote:
> guacamole works and is perfectly usable - are you saying this was all a > "red herring" and it was working with web sockets all the time? :) > The log messages within the Chrome dev tools were red herrings, yes. You can REST assured that they are just normal REST responses, leveraging appropriate HTTP status codes. The error from Apache was not a red herring, but has been (somehow) corrected. In which case I wasted quite a few hours browsing logs! Is there an easy > way to check? If I reload in chrome devtools i see a websocket in ws but > size is 0 B and it's not moving. Using the server for a few minutes > requests are increasing slowly, through the download of tiny png mouse > cursor files. > If you do not see a huge list of HTTP requests to "tunnel" (the endpoint for the HTTP tunnel), and you do not see a warning within the Tomcat logs from Guacamole regarding the HTTP tunnel being used, then you are using the WebSocket tunnel and all is well. The requests that you *do* see are probably just the other various REST API requests. Michael Jumper CEO, Lead Developer Glyptodon Inc <https://enterprise.glyptodon.com/>.
