your guacamole app front end managed by tomcat is not connected to guacd. I
think you missed the step of linking the guacd config folder contents to
the tomcat web app.

On Sun, Aug 1, 2021 at 8:05 AM Mauro Condarelli <[email protected]> wrote:

>
>
> I am trying to understand how to correctly setup Guacamole... and failing.
>
> Question is: how am I supposed to troubleshoot connection problems in
> Dockerized Guacamole?
>
> All documentation I found (pointers welcome) deal with standard
> installation
> (non-dockerized, direct editing of guacamole.properties and
> user-mapping.xml)
> and I simply do not know where to look to understand where I goofed.
>
> Some installation details follow.
>
> I installed Guacamole using Docker containers essentially as follows:
>
>     docker run --name mcon-guacd -d guacamole/guacd
>     docker run --rm guacamole/guacamole /opt/guacamole/bin/initdb.sh
> --mysql > initdb.sql
>
>     readonly db_user=guacamole
>     readonly db_name=guacamole
>     readonly db_pass=SecurePassword
>     readonly db_root=MoreSecurePassword
>
>     mysql --user=mcon --password="${db_root}" <<_EOF_
>     DROP USER IF EXISTS ${db_user};
>     DROP DATABASE IF EXISTS ${db_name};
>     CREATE DATABASE ${db_name};
>     GRANT ALL ON ${db_name}.* TO '${db_user}'@'%' IDENTIFIED BY
> '${db_pass}';
>     FLUSH PRIVILEGES;
>     _EOF_
>
>     mysql --user=${db_user} --password="${db_pass}" ${db_name} <initdb.sql
>
>     docker run --name mcon-guacamole --link mcon-guacd:guacd \
>         -e MYSQL_HOSTNAME=$(ip route get 1 | sed -n 's/^.*src \([0-9.]*\)
> .*$/\1/p') \
>         -e MYSQL_DATABASE=${db_name} \
>         -e MYSQL_USER=${db_user} \
>         -e "MYSQL_PASSWORD=${db_pass}" \
>         -d -p 8080:8080 guacamole/guacamole
>
> I had to allow connections from the net to my mariadb server and also
> install nginx
> reverse proxy to access the container from outside; I can provide details
> but I don't
> think this is the problem.
>
> I can log into Guacamole and use administrative login to setup users (one
> in particular,
> the one I'm using for tesing, has full admin rights) and I'm trying to
> setup connections.
>
> I was able to share localhost desktop via xrdp, so I'm reasonably sure
> basics are OK.
>
> I also tried to setup a ssh connection to a nearby machine.
> To keep things simple I filled only a few fields:
>
>     EDIT CONNECTION
>         Name (sb001)
>         Protocol (SSH)
>     PARAMETERS
>         Network
>             Hostname (192.168.2.211)
>
> Problem:
>
> When I try to connect there's a very long initial delay (probably a net
> timeout) displaying:
>
>     Connected to Guacamole. Waiting for response...
>
> then I see the Login as: prompt but when I type my username echo stops
> after exactly 7 chars (username is 11 chars long) and just sits there. When
> I (blindly) hit Return I get a box with the following message:
>
>     An internal error has occurred within the Guacamole server,
>     and the connection has been terminated.
>     If the problem persists, please notify your system administrator,
>     or check your system logs.
>
> Unfortunately I am the "system administrator" and I cannot find any
> relevant log;
> specifically using :
>
>     docker logs mcon-guacamole
>
> does not show any sign of attempted connection and I don't know how to
> debug this.
>
> I checked and I can correctly ssh to given machine both from host (where
> docker runs)
> and from the container (i.e.: from within: "docker exec -it mcon-guacamole
> /bin/bash").
>
> I also tried installing on my local development machine.
> Same basic installation but no nginx reverse proxy.
>
> I get "almost" the same behavior with it:
> difference is when trying connection (to the same host) I immediately get
> the:
>     An internal error...
> message; no wait and no Login as:.
>
> Definitely I'm missing something :(
> If someone can point me in the right direction...
>
> Thanks in Advance
> Mauro
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to