Quick update, now it works after a few reboot, I have change nothing!

Now also after a reboot and no interaction with the system, I can connect to any devices via any flavour.

I'm feel confused.

Best regards,

Alessandro

Il 13/12/2022 15:03, Alessandro Sironi ha scritto:

Here what I have after a reboot:


 $ sudo systemctl status guacd
* guacd.service - LSB: Guacamole proxy daemon
     Loaded: loaded (/etc/init.d/guacd; generated)
     Active: active (running) since Tue 2022-12-13 11:50:02 CET; 2min 13s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 526 ExecStart=/etc/init.d/guacd start (code=exited, status=0/SUCCESS)
      Tasks: 1 (limit: 4179)
        CPU: 80ms
     CGroup: /system.slice/guacd.service
             `-598 /usr/local/sbin/guacd -p /var/run/guacd.pid

dic 13 11:50:02 hcl systemd[1]: Starting LSB: Guacamole proxy daemon...
dic 13 11:50:02 hcl guacd[527]: Guacamole proxy daemon (guacd) version 1.4.0 started
dic 13 11:50:02 hcl guacd[526]: Starting guacd:
dic 13 11:50:02 hcl guacd[527]: guacd[527]: INFO: Guacamole proxy daemon (guacd) version 1.4.0 started
dic 13 11:50:02 hcl guacd[526]: SUCCESS
dic 13 11:50:02 hcl guacd[598]: Listening on host 127.0.0.1, port 4822
dic 13 11:50:02 hcl systemd[1]: Started LSB: Guacamole proxy daemon.


IPv6 is disabled, if I manually start guacd (/usr/local/sbin/guacd) it start but I stil can't connect to any remote devices.

If I manually start guacd in debug mode:

$ sudo /usr/local/sbin/guacd -L debug -f

guacd[1475]: INFO:      Guacamole proxy daemon (guacd) version 1.4.0 started guacd[1475]: DEBUG:     Successfully bound AF_INET socket to host 127.0.0.1, port 4822
guacd[1475]: INFO:      Listening on host 127.0.0.1, port 4822

and if I try to connect to some remote device:

...................

guacd[1475]: INFO:      Creating new client for protocol "rdp"
guacd[1475]: INFO:      Connection ID is "$e640ec35-1d19-45b7-ac66-e7d815f86510"
guacd[1501]: DEBUG:     Processing instruction: size
guacd[1501]: DEBUG:     Processing instruction: audio
guacd[1501]: DEBUG:     Processing instruction: video
guacd[1501]: DEBUG:     Processing instruction: image
guacd[1501]: DEBUG:     Processing instruction: timezone
guacd[1501]: DEBUG:     Parameter "console" omitted. Using default value of 0. guacd[1501]: DEBUG:     Parameter "console-audio" omitted. Using default value of 0. guacd[1501]: DEBUG:     Parameter "disable-auth" omitted. Using default value of 0.
guacd[1501]: INFO:      Security mode: Negotiate (ANY)

...................

and it works!

What could be the issue?

I can leave it running in debug mode for the moment, but IMHO it's not a good idea.

Best regards,

Alessandro

Il 12/12/2022 19:06, Alessandro Sironi ha scritto:


Il 12/12/2022 18:59, Michael Jumper ha scritto:
On Mon, Dec 12, 2022, 9:36 AM Alessandro Sironi <[email protected]> wrote:

    Hello all,

    I'm facing a very strange issue on my fresh install of guacamole
    on a
    raspberry Pi4 4GB.

    After ending my installation and configuration (extension enabled:
    mysql, LDAP, TOTP and branding, I had restored a DB from an old
    installed guacamole that work) I can't connect into any
    connection I've
    setted up, then I've look into catalina.out but I've find nothing
    intresting (just "connection refuse" as error), so I've put
    guacd into
    debug mode (/usr/local/sbin/guacd -L debug -f) and then I had
    try to
    connect again, well, it works on every connections of every flavour
    (SSH, VNC, Telnet, RDP), so I have stop again guacd and restart
    it in
    normal way, now none of the connetions works and the only log I
    have is
    a "connection refuse".

    What should I do to better debug this issue? Anyone have idea on
    what's
    going on this Pi?


It sounds like your guacd service is just not set up to start on boot, so it's only running when you manually start it.
Nope, it start on boot (I've checked it via systemctl and it's up and running)

Depending on how "localhost" is defined within your system, it's also possible that guacd is listening on IPv6 while the webapp is trying to connect to IPv4 (or vice versa). If you're positive the guacd service is running, I'd check what guacd says in the logs regarding the address it's listening on.

- Mike

It's listening on IPv4, infact if I manually stop it and then manually start it in debug mode, connections works, if I manually stop it again and manually start it via systemctl, connections stop working.

ATM I'm reaching guacamole webpage via tomcat, I'm not proxied it via apache as I usually do (I'll check that all works w/out nothing than guacamole, before put other things in).

Thanks for your reply,

Alessandro

Reply via email to