On Fri, Jul 5, 2019 at 11:18 AM cram < [email protected]> wrote:
> Hi, > I am trying to configure a load balancing group for rdp connections. > I have created the group and added 2 connections and have set the max user > and max user per connection to 50. > But when I try to connect to the group, it throws a Connection error: The > Guacamole server is denying access to this connection because you have > exhausted the limit for simultaneous connection use by an individual user. > Please close one or more connections and try again. > If you want to allow any individual user to establish multiple, simultaneous connections to the group, you will need to set the "Maximum number of connections per user" setting on the connection group. By default, the database authentication extensions will limit the number of connections on a per-user basis so that a single user will not be able to exhaust the pool of connections within the group on their own. > There are no active connections when I checked the Active users tab. > Are you connecting to Guacamole through a proxy or reverse proxy that may not be correctly configured for WebSocket? Misconfigured support for WebSocket within a proxy can result in just enough of WebSocket functioning that the initial connection attempt succeeds and Guacamole notes that the connection is in use. Meanwhile, unknown to Guacamole, the connection fails on the client side due to the mishandled WebSocket connection. The client side, assuming WebSocket has failed entirely, then tries to fallback to HTTP, which Guacamole refuses to allow since it still believes the connection established via WebSocket is open. If default concurrency restrictions for connection groups are overridden, the symptoms of the above would disappear while the underlying problem remains. As no such default restrictions apply to connections, this may be why you are able to use the connections within the group directly. When I click on the connections directly instead of the group it works fine. If you set "Maximum number of connections per user" on the connections themselves rather than the group containing them, that combined with misconfigured WebSocket (see above) may be why. - Mike
