Oh definitely will not be network then. If it is a vm did you try adding more cpu on one host running guacd and increase testing? CPU maybe struggling with 50-60 connections. I will start by increasing the CPU to 3 or 4 and see if that helps.
Another thing which I’m trying to google which I have not found an answer is about linssh2 possible limits. But before you go down that road try increasing CPU and see if there is difference. On Sun, Jul 27, 2025 at 11:13 PM Alex_Yin <[email protected]> wrote: > > Hi，the guacd is running separately from guacamole client, and the server > of one guard is 2C4G。I'm not sure about the speed between the > guacamole-client and guacd, but when connecting two guacds, the upper limit > can reach 120, so the speed should be enough. There is no limit on the > number of TCP connections and the speed between guacd and the connected > server. > Alex_Yin > [email protected] > > ---- Replied Message ---- > From geek 2gether<[email protected]> > <[email protected]> > Date 07/28/2025 11:03 > To <[email protected]> <[email protected]> > Subject Re: SSH Connection Limit of 60 per guacd > Thank you for sharing. Do you mind providing the specs of your server? Is > the guacd running separately from guacamole client ? If so what’s the > specs? Ram and CPU? What’s the network speed between guacd and the client? > > > On Sun, Jul 27, 2025 at 11:00 PM Alex_Yin <[email protected]> wrote: > >> >> Hello, I am doing stress testing on my own guacamole and found that one >> guacd can only connect to 60 ssh connections. When it exceeds 60, it will >> display "SSH handshake failed” (port 81 is the mapping of port 22). When I >> use 2 guacds to connect (using elb for load balancing), the upper limit is >> 120. >> My guacd is deployed on a centos 7.9 server. I see that the establishment >> of ssh uses the “libssh2_session_handshake" function, but the number of fds >> on the server should be sufficient. I want to know what causes this 60 >> limit. >> >> >> Alex_Yin >> [email protected] >> >
