guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henrique Seganfredo <>
Subject Re: Problem starting Guacamole under Tomcat 8
Date Wed, 08 Aug 2018 05:36:18 GMT
Problem solved. Some inputs on my progress since then, with important tips:

1) mysql IP binding was corrected. File /etc/mysql/mysql.conf.d/mysql.cnf
was the right one. bind-address set to (which means any interface).
mysql sql does not support multiple ip adresses to bind to and data could
come from localhost (as a mysql admin tool) or from the guacamole

2) Ctrl-Alt-Shift combination for menu access is a must if you do not want
to erase faulty connections directly on the mysql tables.

3) A bad default connection setting may upset new users that are not aware
of tip #2 since will be stuck at some blank or looping connecting screen
(see #4).

4) Left GUACD parameters empty for each new connection created on the web
interface. The only way to make it work. Using the guacd dockered-ip
( gave refused connections, even with disabled firewall (ufw)
and returning ok from a cat /dev/tcp/ Guess the linking
between the guacamole and guacd containers has some trickery - I am not up
to go deep into docker networking.

5) Used docker run --restart-always to make the guacd and guacamole
containers cycle during host reboots. Docker itself already set as a

6) Guacamole container as run with MYSQL_HOSTNAME equal to the real host IP
and the the dockered one (

7) Shared clipboard support seems buggy. Best behavior was under Internet

1) Will look https over tomcat. All plain tcp even for logon is terrible.
2) Configure vncserver to act as a service.

Thanks for the feedback, hope someone save time from this tips in the

On Sun, Aug 5, 2018 at 4:38 AM, Henrique Seganfredo <
> wrote:

> I am providing the "dockered" localhost IP. On the localhost I typed ip
> addr and wrote down the docker0 address.
> 4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
> state UP group default
>     link/ether 02:42:76:00:92:73 brd ff:ff:ff:ff:ff:ff
>     inet brd scope global docker0
> I found the IP for the guacamole container as guacd container
> is at
> Changed my.cnf (mysql config file) to include the following:
> [mysqld]
> bind-address =
> Checking netstat:
> henrique@homeserver1:~$ sudo netstat -tlnp
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address           Foreign Address
> State       PID/Program name
> tcp        0      0*
> LISTEN      14024/mysqld
> Looks like the bind-address configuration is not being effective. I will
> go deeper on this issue.
> On Sun, Aug 5, 2018 at 3:32 AM, Mike Jumper <>
> wrote:
>> On Sat, Aug 4, 2018, 23:26 Henrique Seganfredo <>
>> wrote:
>>> I did the docker way to speed things up, but I am facing a communication
>>> error from inside the container to the local mysql I did install for
>>> metadata.
>>> Acessing http://localhost:8080 /guacamole returns a blank screen, but
>>> source code is available, it has content related to logged in or logged out
>>> guacamole users.
>> The contents of index.html are static. The dynamic aspects of the webapp
>> are handled via JavaScript and REST requests. It is the failure of one or
>> more of those requests which is causing the interface to abort and display
>> nothing.
>>> Container guacamole is up (I supposed DB communication was fine):
>>> CONTAINER ID        IMAGE                 COMMAND
>>> CREATED             STATUS              PORTS                    NAMES
>>> 1e9b92211476        guacamole/guacamole   "/opt/guacamole/bin/…"   2
>>> minutes ago       Up 2 minutes>8080/tcp
>>> some-guacamole
>>> 88fa3ae48028        guacamole/guacd       "/usr/local/sbin/gua…"   About
>>> an hour ago   Up 45 minutes       4822/tcp                 some-guacd
>> If there are failures in communication with the database, those failures
>> will only become apparent when trying to use the webapp (log in, etc.). No
>> attempts are made to communicate with the database until there are user
>> requests to service.
>>> Seeing the docker log output I get this:
>>> 06:09:51.658 [http-nio-8080-exec-3] ERROR
>>> - Unexpected internal error:
>>> ### Error querying database.  Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
>>> Communications link failure
>> What address/hostname are you providing to Guacamole for your MySQL
>> server?
>> - Mike

View raw message