You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Nick Couchman <vn...@apache.org> on 2025/09/22 17:16:57 UTC
Re: Unable to login with version 1.6.0
On Tue, Jul 8, 2025 at 9:37 AM Erik Dittert <q1...@gmail.com> wrote:
> Nope, same Issue also with MYSQL_USERNAME :(
>
> Am 08.07.2025 um 14:47 schrieb Tom Eaton:
> > You’ve got a typo in MYSQL_USERNAME, that might be the issue.
> >
> >
> >
> >> On 8 Jul 2025, at 13:43, Erik Dittert <q1...@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> i want to use this compose:
> >>
> >> # networks
> >> # create a network 'guacnetwork_compose' in mode 'bridged'
> >> networks:
> >> guacnetwork_compose:
> >> driver: bridge# services
> >> services:
> >> # guacd
> >> guacd:
> >> container_name: guacd_compose_dev
> >> image: guacamole/guacd:1.6.0
> >> environment:
> >> ACCEPT_EULA: "Y"
> >> LOG_LEVEL: "debug"
> >> networks:
> >> guacnetwork_compose:
> >> restart: always
> >> volumes:
> >> - ./drive:/drive:rw
> >> - ./record:/var/lib/guacamole/recordings:rw
> >> # guacamole
> >> guacamole:
> >> container_name: guacamole_compose_dev
> >> depends_on:
> >> - guacd
> >> environment:
> >> GUACD_HOSTNAME: guacd
> >> GUACAMOLE_HOME: /opt/guacamole
> >> MYSQL_ENABLED: true
> >> MYSQL_HOSTNAME: 192.168.62.25
> >> MYSQL_PORT: 3306
> >> MYSQL_DATABASE: guacamole1
> >> MYSQL_USERNAMSE: guacamole
> >> MYSQL_PASSWORD: xxxxxxxxxxxxxxxxxxxxxxxx
> >> MYSQL_DRIVER: mysql
> >> MYSQL_SSL_MODE: disabled
> >> MYSQL_AUTO_CREATE_ACCOUNTS: true
> >> LOG_LEVEL: "debug"
> >> LDAP_ENABLED: true
> >> LDAP_HOSTNAME: 192.168.62.30
> >> LDAP_USER_BASE_DN: DC=xxxxxxxxxxxxx
> >> LDAP_PORT: 389
> >> LDAP_ENCRYPTION_METHOD: none
> >> LDAP_SEARCH_BIND_DN: CN=xxxxxxxxxx,CN=Users,DC=xxxxxxxxxxx
> >> LDAP_SEARCH_BIND_PASSWORD: xxxxxxxxxxxxxxxxx
> >> LDAP_USER_SEARCH_FILTER: (&(objectClass=user)(|
> >> (memberOf=cn=FG_IT,cn=groups,dc=xxxxxxxxxxx)
> >> ))
> >> LDAP_USERNAME_ATTRIBUTE: "sAMAccountName"
> >> LDAP_GROUP_BASE_DN: "dc=xxxxxxxxxxxx"
> >> LDAP_GROUP_NAME_ATTRIBUTE: "CN"
> >> LDAP_GROUP_SEARCH_FILTER:
> (&(objectClass=group)(|(cn=FG*)(cn=Proj*)(cn=FA*)))
> >> REMOTE_IP_VALVE_ENABLED: true
> >> REMOTE_IP_VALVE_REMOTE_IP_HEADER: x-forwarded-for
> >> PROXY_BY_HEADER: x-forwarded-by
> >> REMOTE_IP_VALVE_PROTOCOL_HEADER: X-Forwarded-Proto
> >>
> >> #performance
> >> disable_bitmap_caching: true
> >>
> >> TOTP_ENABLED: true
> >> TOTP_ISSUER: "guac.xxxxxxxxxxxxxxxxxxxxx"
> >> TOTP_DIGITS: "6"
> >> TOTP_PERIOD: "30"
> >> TOTP_MODE: "sha1"
> >>
> >> RECORDING_SEARCH_PATH: '/var/lib/guacamole/recordings'
> >> WEBAPP_CONTEXT: "ROOT"
> >>
> >> image: guacamole/guacamole:1.6.0
> >> links:
> >> - guacd
> >> networks:
> >> guacnetwork_compose:
> >> volumes:
> >> - ./extensions:/opt/guacamole/extensions
> >> - ./drive:/drive:rw
> >> - ./record:/var/lib/guacamole/recordings:ro
>
Sorry, digging back through old e-mails, and can't remember if this one has
been addressed, yet. Mapping through the /opt/guacamole/extensions folder
is almost certainly killing your ability to log in. The proper way to deal
with deploying custom extensions is to do the following:
* Create a template Guacamole home folder that has an "extensions"
sub-folder on your host system (or in K8s, etc.)
* Map this template folder through to a location that is *not* part of the
Guacamole install - something like /custom_home:/custom_home.
* Set the GUACAMOLE_HOME variable for the container to the template
location: GUACAMOLE_HOME=/custom_home
The guacamole container will take the contents of that template/custom home
folder and put together the rest of the options to create the home folder
the web application will actually use.
See:
https://guacamole.apache.org/doc/gug/guacamole-docker.html#custom-extensions-and-guacamole-home
-Nick