Thanks, Nick. Let me elaborate more on how the system is built. The guacd server is running on Ubuntu 18.04.5 LTS, under port 4822. I have upgraded to version 1.2.0 yesterday while trying to solve the issue (Which hasn't been solved yet I'm pretty sure).
The Guacamole web server is running also on Ubuntu 18.04.4 LTS, as the Web application running on Tomcat 7, as a .war application. There is no reverse proxy for this web server. We only added SSL to the Tomcat configuration. (Today I'm going to add NGINX, with the hope that it will solve this). The web server running on port 8443 (Also on 8080, but we use 8443 for SSL encryption). This application is deployed with Maven, coded on Java. We have a Java application that we have coded, using the GuacamoleHTTPTunnelServlet class (We extended it and added some features). Basically, we needed to add an authorization layer with our system tokens, and also we needed to allow multiple tunnels to the same connection (For example, one user is controlling the remote connection and 3 more people watch it live). This is the class that we coded: https://codeshare.io/G7ozYr <https://codeshare.io/G7ozYr> The frontend is running on our site, importing 'guacamole-common-js/all.min.js', and creating a tunnel using new Guacamole.HTTPTunnel and new Guacamole.Client. The view of the remote connection is wrapped in our site inside a div. I believe that the problem located in one of the following: 1. The Java Application because this is the only part that is not used defaultly. 2. The communication between the Guacamole Webserver to the Guacamole Server Thanks again, And if you need any more information just let me know! -- Sent from: http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
