You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "peter (Jira)" <ji...@apache.org> on 2022/01/25 11:48:00 UTC

[jira] [Created] (GUACAMOLE-1521) ipv4: Creation of WebSocket tunnel to guacd failed

peter created GUACAMOLE-1521:
--------------------------------

             Summary: ipv4: Creation of WebSocket tunnel to guacd failed
                 Key: GUACAMOLE-1521
                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1521
             Project: Guacamole
          Issue Type: Bug
          Components: guacamole
    Affects Versions: 1.4.0
         Environment: This is Ubuntu 18.04 with xrdp.
            Reporter: peter


After upgrading from Guacamole 1.3.0 to 1.4.0 users cannot login. Reverting to 1.3.0 fixed the issue. Error message of the web frontend is:

"Die Verbindung wurde aufgrund eines internen Fehlers im Guacamole Server beendet. Sollte dieses Problem weiterhin bestehen informieren Sie Ihren Systemadministrator oder überprüfen Sie die Protokolle."

(internal guacamole error)

I checked the logs and found this:

 
{code:java}
/var/log/tomcat8/catalina.out:
1:19:48.768 [http-nio-8080-exec-5] INFO  o.a.g.r.auth.AuthenticationService - User "test" successfully authenticated from xxx.xxx.xxx.xxx.
11:19:49.257 [http-nio-8080-exec-3] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket tunnel to guacd failed: java.net.ConnectException: Verbindungsaufbau abgelehnt (Connection refused)
11:19:49.374 [http-nio-8080-exec-4] ERROR o.a.g.s.GuacamoleHTTPTunnelServlet - HTTP tunnel request failed: java.net.ConnectException: Verbindungsaufbau abgelehnt (Connection refused)
(END){code}
Before the upgrade, guacd started up like this:

 

 
{code:java}
Jan 08 15:21:24 host guacd[2003]: guacd[2003]: INFO:        Guacamole proxy daemon (guacd) version 1.3.0 started
Jan 08 15:21:24 host guacd[2003]: Listening on host 127.0.0.1, port 4822
Jan 08 15:21:24 host guacd[2003]: guacd[2003]: INFO:        Listening on host 127.0.0.1, port 4822{code}
After the upgrade:

 

 
{code:java}
Jan 25 11:23:56 host guacd[2026]: guacd[2026]: INFO:        Guacamole proxy daemon (guacd) version 1.4.0 started
Jan 25 11:23:56 host guacd[2026]: guacd[2026]: INFO:        Listening on host ::1, port 4822
Jan 25 11:23:56 host guacd[2026]: Guacamole proxy daemon (guacd) version 1.4.0 started
Jan 25 11:23:56 host guacd[2026]: Listening on host ::1, port 4822{code}
Notice the different host 127.0.0.1 vs ::1. Since 1.4.0 guacd seems to listen on ipv4 and ipv6 interfaces, whereas in the previous version it seems to start only on ipv4 (maybe https://issues.apache.org/jira/browse/GUACAMOLE-1190 is related). I then tried to set the following configuration in /etc/guacamole/guacamole.properties:
{code:java}
guacd-hostname: 127.0.0.1{code}
But it seems to be ignored. Even if I set guacd-port guacd still uses the old one after restarting the service. As a last resort I completely disabled ipv6 on that system and this does the trick. guacd is running on 127.0.0.1 again and users can log in.

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)