Re: Guacamole 1.4.0 doesn't start with "Unable to bind socket to any addresses" 1.3.0 however works fine.

[Nick Couchman]

On Tue, Feb 22, 2022 at 5:57 PM aeb...@aebian.org <aeb...@aebian.org> wrote:

> Greetings everyone,
>
> I have "upgraded" a guacamole 1.3.0 installation to 1.4.0 but for whatever
> reason it doesn't want to start at all.
> The error I get is this:
>
> =========================================================================================
> Feb 22 23:40:10 nhmucrmgw01 systemd[1]: Starting LSB: Guacamole proxy
> daemon...
> ░░ Subject: A start job for unit guacd.service has begun execution
> ░░ Defined-By: systemd
> ░░ Support: https://www.debian.org/support
> ░░
> ░░ A start job for unit guacd.service has begun execution.
> ░░
> ░░ The job identifier is 564.
> Feb 22 23:40:10 nhmucrmgw01 guacd[1101]: Guacamole proxy daemon (guacd)
> version 1.4.0 started
> Feb 22 23:40:10 nhmucrmgw01 guacd[1100]: Starting guacd:
> Feb 22 23:40:10 nhmucrmgw01 guacd[1101]: guacd[1101]: INFO:
> Guacamole proxy daemon (guacd) version 1.4.0 started
> Feb 22 23:40:10 nhmucrmgw01 guacd[1101]: Unable to bind socket to any
> addresses.
> Feb 22 23:40:10 nhmucrmgw01 guacd[1101]: guacd[1101]: ERROR:        Unable
> to bind socket to any addresses.
>

Try creating a guacd.conf file and adding a the following:

[server]
bind_host = 127.0.0.1
bind_port = 4822

And then try to start guacd and see if that works.

-Nick

>