Take a peek at the docs coverying proxying guac through Nginx (and if you already have, double-check):
http://guacamole.apache.org/doc/gug/proxying-guacamole.html#nginx It's fairly easy for misconfiguration to result in WebSocket effectively being blocked. Guac will then fallback to HTTP, which is fine but (1) is under tighter browser restrictions in terms of max connections per domain and (2) will have slightly higher input latency. You'll see a warning in the Tomcat logs if HTTP is being used as a fallback. - Mike On Tue, Nov 6, 2018, 21:44 doyouhas <zjpia...@gmail.com wrote: > Not seeing anything specifically related to HTTPS/fallback. Since you > mentioned that, however, I went ahead and disabled HTTPS on my nginx proxy > and that seems like it may be the culprit. I have a connection going right > now and it has been solid for the past five minutes. What settings do I > need > to look at regarding HTTPS? > > > > -- > Sent from: > http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/ >
