I may have had a similar problem. After a few days/weeks, connections
through guacamole would take a long time. I could connect directly to the
computers via ssh or rdp just fine from a different computer in my lan.
I realized RAM usage on my server hosting guacamole was very high, and it
looked t
I had to build mine. If I recall correctly, all I had to put in it was
user-mapping.xml
On Thu, Jan 16, 2020, 05:56 BenDDD wrote:
> Hi everyone,
>
> I have installed Guacamole server and client from Git by following this doc
> : https://guacamole.apache.org/doc/gug/installing-guacamole.html
> <
I use it myself to act as my gateway into my network. Instead of opening
several ports for RDP/VNC/SSH to various machines (I used non-standard
ports, so 3389 is not open), I instead have https access to guacamole on my
webserver, and then from there I can connect to whichever systems I have
enable
Paul,
Wouldn't VNC do what you accomplish? I used to use it extensively to
connect in to a coworker's computer. If I recall correctly, I used UltraVNC
and we could disable our keyboard/mouse so we wouldn't disturb them (and
they wouldn't even know we were there), we could black out their screen, o
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
I've got Guacamole installed, and it's great as long as I stay inside my
local network. I've got remote.mydomain.com forwarding to my static
address, and then a reverse proxy forwarding that to Guacamole. I'm running
Debian 9, Apache 2.4.25, Tomcat 9.0.22, and Guacamole 1.0.0.
Apache Reverse Proxy
