Thanks, just seemed odd that two browsers on the same machine (one incognito, one normal on separate accounts) allow the first connection to separate VMs in the connection group. However, an issue arrives when I disconnect both browsers and log out back in with the incognito browser to the same connection group it works but then the normal browser throws that error.
Connection Error: This connection is currently in use, and concurrent access to this connection is not allowed. Please try again later. But, this seems like a rather minor issue when I look at it more and if it is intended maybe it is no big deal. Michael Barkdoll On Fri, May 3, 2019 at 2:19 PM Mike Jumper <[email protected]> wrote: > On Fri, May 3, 2019 at 8:48 AM Michael Barkdoll <[email protected]> > wrote: > >> ... >> Should've read: >> Refreshing first Chrome browser *doesn't* update the connection string: >> https://host/guacamole/#/client/MQBnAG15c3Fs >> <https://localhost/guacamole/#/client/MQBnAG15c3Fs> >> >> That actually appears to be the expected behavior since this is a >> connection group url (I'm guessing). >> > > Yes, that's the expected behavior. The URL will not change. The balancing > across underlying connections happens internally within the server. It is > intentionally not exposed on the user facing side. > > - Mike > >
