Yes, it is running. I had to add the guacd.conf file to get it to stop listening to ::1 port 4822. It is now listening to 127.0.0.1 port 4822
 
root@guac:/home/theadmin# systemctl status guacd
● guacd.service - LSB: Guacamole proxy daemon
     Loaded: loaded (/etc/init.d/guacd; generated)
     Active: active (running) since Tue 2022-02-22 09:46:45 CST; 1h 17min ago
       Docs: man:systemd-sysv-generator(8)
    Process: 763 ExecStart=/etc/init.d/guacd start (code=exited, status=0/SUCCE>
      Tasks: 1 (limit: 4639)
     Memory: 13.7M
        CPU: 20ms
     CGroup: /system.slice/guacd.service
             └─767 /usr/local/sbin/guacd -p /var/run/guacd.pid
Feb 22 09:46:45 guac systemd[1]: Starting LSB: Guacamole proxy daemon...
Feb 22 09:46:45 guac guacd[765]: Guacamole proxy daemon (guacd) version 1.4.0 s>
Feb 22 09:46:45 guac guacd[763]: Starting guacd:
Feb 22 09:46:45 guac guacd[765]: guacd[765]: INFO:        Guacamole proxy daemo>
Feb 22 09:46:45 guac guacd[763]: SUCCESS
Feb 22 09:46:45 guac systemd[1]: Started LSB: Guacamole proxy daemon.
Feb 22 09:46:45 guac guacd[767]: Listening on host 127.0.0.1, port 4822
 
Sent: Tuesday, February 22, 2022 at 10:51 AM
From: "Nick Couchman" <[email protected]>
To: [email protected]
Subject: Re: Problems with GuacamoleHTTPTunnelServlet
On Tue, Feb 22, 2022 at 11:01 AM Jim Rx <[email protected]> wrote:
Hello,
 
So I've got 1.4.0 up and going. I'm now trying to connect and test to remote stations, and am having no luck.
 
-The machines have IP connectivity
-Attempts to connect (RDP) to both a Centos7 VM and a Windows10 VM fail. Two different messages show up in catalina.out:
  HTTP tunnel request failed: Connection to guacd timed out
  HTTP tunnel request failed: No such tunnel
 
I have the connections set up for IP/3389, No encryption, Any security type, and ignore the server certificate. I have verified that the RDP/XRDP service is running on both target VMs.
 
Any suggestions where to look?
 
 
Is guacd running? If so, is it listening on the IPv4 address (127.0.0.1)? You may need to configure it to listen on IPv4 by setting up a guacd.conf file with the bind_host set to 127.0.0.1. Newer Linux distros tend to default to IPv6, particularly for loopback traffic, and this won't work between Tomcat and guacd by default.
 
 
-Nick
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Reply via email to