On Tue, May 31, 2022 at 4:56 PM ralph strebbing <blackbirdra...@gmail.com> wrote:
> On Tue, May 31, 2022, 4:44 PM Lee Doughty <l...@virginiacyberrange.org> > wrote: > >> Hello Guacamole Community, >> >> I tried asking this a few weeks ago, but it looks like there was not a >> lot of traction on this idea.. but I wanted to try one more time before I >> gave up on it. >> >> I think it would be a great feature to stop auto-reconnect attempts that >> are simply not connecting after several dozen attempts. I've seen in our >> logs that some users hit the "Reconnect" button or otherwise get into a >> reconnect loop, then leave the tab open for hours *or days*. This >> results in our guacamole server getting a ping every minute or so from a >> user trying to connect to a VM that is not available, and they just leave >> it retrying over and over again. >> >> It would be nice to at least require user interaction to resume the >> connection attempts... So users have to return to the tab every N attempts >> to restart the countdown, instead of the current never-ending loop... I'm >> not suggesting any value for N... because any reasonable value would be >> nice over infinite. My record was somewhere in the ballpark of 7,000 >> attempts (5 days) before the user was kind enough to close the tab and stop >> poking our Guacamole server. >> >> Is this something that can make it into an upcoming Guacamole release? >> > > This is also something that would be nice as a "per-device" or a per guacd > config value to adjust (or a default value if not set). > > Today Guacamole attempts to handle this based on the reason for the disconnect. If the disconnect is detected to be a "normal" disconnect (user logs off or disconnects from inside a RDP session, for example), Guacamole should not automatically attempt to reconnect. If the disconnect is unexpected - network drops, mainly - Guacamole will reconnect. That said, I think it would be useful to have an option where you could disable the auto-reconnect, or set a limit on the number of reconnect attempts, on a per-connection basis. Seems related to this particular Jira issue: https://issues.apache.org/jira/browse/GUACAMOLE-1126 -Nick >
