8gears/containerized-guacamole

Apache Guacamole out of the box compose setup with Nginx Reverse Proxy, Lets Encrypt. Simple and easy deployable with Docker Compose. Uses only Official Guacamole Docker Images

containerized-guacamole's Issues

PostgreSQL image needs to stay at 9.6

First of all, many thanks for this repository. It is plain and simply wonderful.

I had though an issue when trying to deploy a new system. I was getting an authentication error in PostgreSQL. In order to solve this I had to make the postgresql container to stick to version 9.6 and recreate the database from the init step.

use websocket

hey there
is it somehow possible to use websocket connection with this project?
according to guacamoles documentation it helps with performance.

Custom .jar file

Hi

Great work on this. Your comment stating that although this repo is 3 years old the script uses latest images was useful in helping me find and use this.

The custom branding.jar file you are able to add within the guacamole/guacamole:latest container /extensions folder seems to delete after restarting the container. There is one .jar file in there currently (guacamole-auth-jdbc-postgresql-1.3.0.jar)
Any ideas on why this is and any potential fixes to allow a custom login page.

remove /guacamole/

hey there

as there is only guacamole running on this docker.compose I think it would make sense to run directly @root.

the branding.jar file dissapears from the volume created as soon as the container is restarted

          the branding.jar file dissapears from the volume created as soon as the container is restarted

Originally posted by @carlostico in #3 (comment)

re-initialize nginx / ssl after domain-change

hey there
I had to move away from my .tk domain. now I don't want to lose my guacamole-config and just rewrote the domain inside .env

but when I restart docker-compose it will provide me with a temporary cert and shows "503 Service Temporarily Unavailable"

is there a way to just re-initialize the nginx-part?

Using the created Nginx & Letsencrypt companion for SSL certs on a different server/IP address

This may be out of scope for here but wanted to ask as i can't seem to get it.
I have this fully working which is great.

I am now looking to use the nginx + letsencrypt containers to help secure an SSL cert for a webserver on a different IP address.

Is this possible?

(I have set up a 'webserver.conf' file in /etc/nginx.conf.d/ - and this is proxying to the correct IP and working - without SSL)

I see how to do it if I wanted to create another docker container within the same server+network but can't figure out how to do it with an existing server on a different IP address!

show remote host ip behind reverse proxy

This setup shows nginx's ip as remote host ip, is there a way to show the real ip behind reverse proxy?

letsencrypt (acme.sh) cannot connect on port 80 for the verification.

I know this project is getting old now, but I was hoping to get it up and running anyways.
It seems to "mostly" work, but I have hit two issues.

Minor detail:
The init-guac-db tries to write the file to /init/initdb.sql which it is not allowed to do. I changed it to /tmp/initdb.sql and that seemed to work.

Real problem:
Letsencrypt/acme.sh does not seem to be able to get the port 80 (http) connection up. The logs show "Connection Refused" for the .well-known/... address. I cannot seem to figure out where the problem is. I dont see the port 80 being blocked anywhere on the system, but It might be caused by something like that somehow. Any ideas?

how to disable LE SSL

Since I will be using my own external reverse proxy server to encrypt the traffic, I need to disable lets encrypt encryption service as built in docker file.

How should I modify the repo?

Not working with port 443 only with port 80

Hi ,
Maybe i am wrong and i missed something .
here is my env file
POSTGRES_USER=guacadb
POSTGRES_PASSWORD=Mypassword

Uncomment if you want to test with dummy certificates

#LETSENCRYPT_TEST=false
VIRTUAL_HOST= mydomain
LETSENCRYPT_HOST=Mydomain
LETSENCRYPT_EMAIL=Mymail

When i followed the process it only work with port 80 . I edited the nginx conf file and i saw that nginx is listening on port 80 not 443. I changed the port and then it worked

initdb script failing

Following the directions, running the initdb container alone gets this output:

Creating network "containerized-guacamole_default" with the default driver
Creating volume "containerized-guacamole_dbinit" with default driver
Creating volume "containerized-guacamole_dbdata" with default driver
Creating containerized-guacamole_init-guac-db_1 ... done
Attaching to containerized-guacamole_init-guac-db_1
init-guac-db_1       | /bin/sh: 1: cannot create /init/initdb.sql: Permission denied
containerized-guacamole_init-guac-db_1 exited with code 2

I looked into the docker-compose file and found that although there's a POSTGRES_PASSWORD env var in .env, it doesn't seem to be used in the docker-compose file. Not sure what else could be causing this issue.

DB initialisation no longer works

Whilst running in the latest version of Docker on an Intel mac:

Attaching to containerized-guacamole-init-guac-db-1
containerized-guacamole-init-guac-db-1  | /bin/sh: 1: cannot create /init/initdb.sql: Permission denied
containerized-guacamole-init-guac-db-1 exited with code 2

My guess is something has changed in the Guacamole Docker image…