Hey all- I've done some digging since my last post about this. Would be grateful for your direction. Happy also to pay for anyone's time if that's an option.
Apologies for this long post. We desperately need some help to get things going for an early customer we just scored. Problem: -->We have an idle timeout (15 mins) working via tigervnc server. The problem is, guacamole then automatically reconnects, which we want to disable. Setup: -->Guac: ubuntu 20.04 (on GCP) + guac 1.4.0 & guac-client built from source + tomcat9 + nginx reverse proxy & ssl + mysql auth -->VM: vnc connection using tigervnc server to Kali Linux (on GCP) Some solution ideas/questions (with contextual info): 1. Here <https://drive.google.com/file/d/1u7xJfJyG0gv5C_pv8vUpIpDNExjYjW87/view?usp=sharing> is a screenshot of the auto reconnect dialogue box that pops up after the VNC server does the idle timeout 2. The dialogue box language matches up with ERROR_CLIENT_203 <https://github.com/apache/guacamole-client/blob/ed7746e0612d569644277a2aa654c5eda4447c8e/guacamole/src/main/frontend/src/translations/en.json#L80> in the guacamole-client source code 3. Client error code 203 is designated as one of the error codes that triggers an auto reconnect in guacClientNotification.js <https://github.com/apache/guacamole-client/blob/7e30b8682a28c50935874e6779281da4c548715e/guacamole/src/main/frontend/src/app/client/directives/guacClientNotification.js#L95> 4. Could I disable the reconnect simply by commenting out line 95 in guacClientNotification.js? (I get that this is not a recommended way to do it) 5. If I do that, can I activate the change simply by restarting guacd or do I need to make the change in source and then reinstall guacamole-client? 6. If modifying guacClientNotification.js is not the way, then what do I need to modify to accomplish my goal? 7. I've seen past listserv messages explaining that GUACAMOLE-208 <https://issues.apache.org/jira/browse/GUACAMOLE-208> might have intended to address this, so perhaps that didn't fully work and guacamole is still not categorizing idle timeout under the proper error code (or maybe it's fixed for rdp but not vnc). However, that seems like a big lift to sort out quickly- I would really welcome a quick hacky solution even if it isn't ideal. Even a way to disable auto-reconnect across the board would be fine for now. 7. Is your ideal rec to do this via an extension? If yes, any pointers to get us started? I've read the documentation, but I don't understand how we could use an extension to override the auto-reconnect trigger. Thank you!! Tushar
