Guacamole is entirely inside the network I'm using, I'm only accessing the client side from an external net.
I actually figured it out a few minutes after hitting send. https://guacamole.apache.org/doc/gug/troubleshooting.html#idm46248436156528 For me, enabling https did the trick (and then web sockets to reduce lag). On Tue, Aug 6, 2019, 15:58 sciUser <shulb...@securitycentric.net> wrote: > Ran in to this myself a while back, unfortunately Guacamole is limited to > networks it can touch. > You may try to add a route to the network you want to reach and see if that > works. > > Thank you > > > > ----- > A Cybersecurity Enablement Company > We don't just run you through the motions, Our labs teach you how to > think! > Known good Guacamole installations > > -- > Sent from: > http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org > For additional commands, e-mail: user-h...@guacamole.apache.org > >
