[
https://issues.apache.org/jira/browse/GUACAMOLE-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524969#comment-17524969
]
Florian Obradovic commented on GUACAMOLE-1190:
----------------------------------------------
Hi.
Just updated 1.3.0 to 1.4.0 on Ubuntu 20.04 x64.
This seems to break things because now guacd is listening on IPv4 only:
!image-2022-04-20-14-41-57-043.png|width=990,height=537!
!image-2022-04-20-14-42-39-072.png|width=581,height=89!
Fixed this by creating /etc/guacamole/guacd.conf with the following content:
{code:java}
[server]
bind_host=127.0.0.1{code}
I left /etc/guacamole/guacamole.properties is untouched with
{code:java}
# Hostname and port of guacamole proxy
guacd-hostname: localhost
guacd-port: 4822{code}
This binds to IPv4 only!
Shouldn't bind_host=localhost result in listening on both IPv4 and IPv6?
* ::1:4822
* 127.0.0.1:4822
Other people seem to have the same issue:
*
[https://www.mail-archive.com/search?l=user%40guacamole.apache.org&q=subject:%22RE%5C%3A+After+Upgrade+1.3+to+1.4+no+connection+working%22&o=newest&f=1]
*
[https://serverfault.com/questions/1083082/guacamole-only-listening-on-ipv6-localhost]
Best regards, Flo.
> guacd cannot bind to IPv6 addresses
> -----------------------------------
>
> Key: GUACAMOLE-1190
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1190
> Project: Guacamole
> Issue Type: Bug
> Affects Versions: 0.9.14, 1.0.0, 1.2.0
> Environment: Linux, IPv6-only
> Reporter: Jonas Zeiger
> Assignee: Mike Jumper
> Priority: Major
> Fix For: 1.4.0
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The guacd daemon can't bind to IPv6 addresses like `::1` due to the server
> socket being restricted to AF_INET.
>
> Thus guacd can't work at all in an IPv6-only environment.
>
> One possible fix is to create the server socket AF_INET6 if no IPv4 address
> is available/specified.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
