Hello Nick and Tobias, Just to mention that I could create an image with guacd 1.6-dev on Debian 12 last week and I will run again the tests this week to see if I can have more than 60 RDP connections. If it works, I will clean the dockerfile and the script used to build guacamole and post it to this thread.
Best regards, Paul From: Nick Couchman <[email protected]> Sent: Monday, January 20, 2025 11:06 PM To: [email protected] Subject: Re: Maximum number of simultaneous RDP connections On Mon, Jan 20, 2025 at 3:22 AM Tobias Feller | OPC <[email protected]<mailto:[email protected]>> wrote: Hi Nick, Hi Paul, i can also confirm this issue with > ~ 60 active Connections. Same environment. Docker, Debian I ran into this problem a time ago with Version 1.5.4 / 1.5.5 and then going back to 1.5.3 to resolve it. In the meantime we now also have a HA-setup: * Loadbalancer with RoundRobin/StickySessions * 2 Guacamole Hosts (docker, guacd,tomcat) * 1 HA (cloud) Postgres DB This morning one of the Host (Debian 11, running 1.5.3) had some problems, and all users connected to the guacamole-host with version 1.5.5. After some time i received the info that users can not connect, because without round-robin the 1.5.5, hit the 60-connection limit. It is maybe possible to provide an offical debian-image instead of ALPINE? Will this be addressed/fixed in 1.6? It's hard to say whether this will be addressed in 1.6.0, because it's been hard to get reliable reproduction of the issue to this point. That's not to say that I doubt that anyone who reports this is actually running into the problem, just that it's difficult to resolve a problem that you cannot deterministically reproduce. If you want to figure out if the problem still exists or has been solved in 1.6.0, the best thing to do would be to build the Docker images yourself and update your environment and see if the problem exists. Regarding moving from Alpine to Debian - I'm sure it's possible; however, the reasons for choosing Alpine as the base image are not arbitrary. I've forgotten exactly why we went that direction in the past, but I believe it was due to the availability of the various libraries that we need for guacd - things like libssh2, FreeRDP, etc. Making that transition to Debian would require a good bit of work to validate that all of the protocols and other features (guacenc) that rely on external libraries. Again, very doable, but not necessarily trivial. Also a small feature request for this kind of this HA-Setup: Is it possible to add a info somewhere in the connection-history from which host the connection was initiated? Maybe via an ENVIRONMENT-VAR "GUCAMOLE_HOST_ID" as prefix/suffix in some existing info (connection name) if defined? It is possible, yes, but not without changes in the code - some changes would need to be made to add a host ID or host name, etc., to the available parameter tokens. -Nick
