We recently updated our guacamole deployment to 1.6.0 and our users have lost the ability to reload the browser tab when connected to a VM. It appears that the websocket tunnel is disconnected on reload and never reconnected. When they reload the tab, the screen goes black and stops receiving updates. The developer console shows that the websocket is gone, and the guacd log shows that the client has disconnected.
We're trying to troubleshoot the issue in the guacamole-client, and have had limited success working with the webpacked client code - some of it can be mapped to sources while other parts are still minified. So, if there are suggestions to make it easier to debug the client, we would appreciate any help getting started. To make matters more complicated, it seems that for some users in some browsers, they _are_ able to reload the browser and the guacamole client websocket does reconnect, but for most users it does not. The other thing we're seeing is - the websocket is sometimes being lost for users who resize their browser window by dragging the window corners. For them, the screen redraws for a bit before it goes black. This problem seems to affect users in Windows on Edge disproportionally, but we've heard reports from other OS and browser configurations, too. We haven't ruled out the possibility that these could be two manifestations of the same bug, which is why I bring it up. I'm happy to provide more details about our setup, if it's relevant - or any of the logs from guacd or tomcat. I wish I had better details to share - we don't see anything obvious in the tomcat guacamole log, in the nginx logs, or in the guacd logs. It looks like the client is hanging up and never trying to reconnect. Thanks!
