I agree with Nick here... My coworker had a task to evaluate performance from Australia to our guacamole in Northern Virginia. Despite using a VPN to jump to Australia before circling back (VA-> Australia->VA), the latency he observed was in the ~1-2 second range. Even if satellites are involved, I can't see a round trip time over 4 seconds being possible without an underlying problem.
In my experience, guacamole has rarely been the failure point if anyone else can access the same connection. It almost always is a problem on the users side... Either network, plug-in/extension, security software, or ISP problem. -Lee On Wed, Jun 22, 2022, 12:21 PM Nick Couchman <[email protected]> wrote: > On Tue, Jun 14, 2022 at 3:17 PM Stefan Bogdan Cimpeanu < > [email protected]> wrote: > >> Hi Antony, >> I agree it could be that, however, it does not explain (in my mind) why >> would the Guacamole server behave differently when the user is from Europe >> or from Australia if the target is still in Australia. >> Is there any special connection happening from the end user all the way >> to the target somehow? >> >> Additionally, can that 15 seconds timeout be increased somehow? >> >> > At this point I do not believe the 15 second time limit can be increased, > but I'd also be surprised if it's actually taking 15 seconds to connect to > the server, even if it's going Australia -> Europe -> Australia. I run a > Guacamole instance in Ashburn, Virginia, and access servers in Singapore > and Australia from that instance, and I don't see intermittent or > consistent issues with that. > > When you hit the failure, check the guacd logs, and possibly start guacd > in debug mode, and see what the error is. Is it really timing out, or is it > throwing some other error? Is there an Azure firewall, ACL, or network > route in place that could be stopping or disrupting traffic from the > Guacamole server to the target server? > > -Nick >
