Taddeusz

Yes, they most definitely block port 80: https://www.cox.com/residential/support/internet-ports-blocked-or-restricted-by-cox.html They don't want people running web servers out of their homes.

I already did just to make sure things haven't changed but Cox Cable blocks port 80.

Wow, this sucks! Our ISP blocks port 80 so there is absolutely nothing I can do but wait and it's already been 3 days.

Not that I'm aware of. You would need to proxy it with Apache or Nginx. I use the Let's Encrypt docker to provide a free cert.

Sorry for my delay in response. The holidays were pretty busy for my family. For my own Windows machines under the Authentication settings in the Guacamole connection I've had to specify NLA for the Security Mode and check to ignore the server certificate. Otherwise it won't connect.

Make sure you’re not putting the host name in the proxy area.

I made a small update to add the Powerline fonts so that the agnoster theme in the Oh My Zsh package will display properly.

Are you looking inside the container? docker exec -it ApacheGuacamole bash

It just dawned on me that the logging that shows up in the Docker log output is just for guacd. The output for the tomcat8 log is separate. It shows up inside the container in /var/log/tomcat8/catalina.out. Unfortunately I'm not sure if there is a way to redirect that log.

Everything in the log is what Guacamole outputs. I'm not sure if there's a way to change it.

I tried to retool this with Alpine but it doesn't have packages for all the dependencies to run or build the Guacamole Server. I've manged to reduce the size by a little bit by separating the build and run dependencies. I then remove all the build dependencies before the final image is created thereby reducing the overall size. But like I said before, the size is mainly due to all the dependencies for the Guacamole Server, Tomcat 8, and MariahDB.

Can you tell me what extension this is and where I may find it so I can test it out?

After investigating this today I've come to the conclusion that this is just going to be how big this is. This is mainly due to the three applications: guacd, tomcat, and mariadb and all their dependencies. I can't see a way to change this. The phusion/baseimage:0.9.22 is only 225MB. Even if I could get it working under the Alpine image it probably wouldn't reduce the overall size by enough to make a huge difference. I even tried using the guacamole/guacd image as a base , which uses CentOS 7 as it's own base, and after installing tomcat and mariadb the completed image before doing anything else was just over 1GB. That was before adding the Guacamole client, plugins, and all the needed scripting. With Alpine I would still need to have some kind of init system to run all the daemons. Maybe someone else could do better?

Dang, never noticed that before. The original project uses phusion baseimage so that's just what I continued with. I'll see if there's a way I can get the size down.

Did you fill out the duo-api-hostname, duo-integration-key, duo-secret-key, duo-application-key properties in your guacamole.properties file with the appropriate information for your account?

That is weird. Are you testing both users on the same machine in the same browser? If that's not the case I would file a bug report with them as this is beyond me. Otherwise at least try from different browsers, not just different browser windows, if not different physical computers at the same time. Personally I've never had more than one user. Just trying to rule out the possibility of multiple Guacamole sessions in the same browser might not behave correctly.

What happens when you click Logout?

Do both users have permission for both connections? If they only have permission for one connection each that's still just one connection.

As nice as Guacamole is this is one of the things that bothers me about it. They designed it so that if there is only one connection configured it will automatically connect to it as well as reconnect to it. The only way out of that situation is to go to the settings and create a second connection. Once there is more than one connection configured it will go to the selection screen upon login and when you want to disconnect you will then have a "Home" option that wasn't available before. I believe the reason they have it configured this way is for single application situations like in a Docker container. The one example I have that I use frequently is the HandBrake Docker. It uses Guacamole internal to the container to connect to the X session to display the HandBrake GUI. It's the only connection available so it automatically connects and is the only connection ever available within the Docker. So, just add a second connection and it will solve your frustration.

Last night I decided to install RC9. My Guacamole is working fine. I'm able to log in and connect to my remote machines. Not sure what the difference might be?

That's how I originally had mine configured at home. My DC died so I decided just to not do a Windows Domain at home since it just added unnecessary complexity and since I've started doing development rather than network admin it doesn't really do anything for me professionally. This is the document I followed to get it working: Guacamole LDAP Authentication with Active Directory Make sure the users that are allowed to use each particular computer are specified

Are you using Windows Active Directory or regular LDAP?

No, since the happiness of our house depends on the server I'm sticking to final releases.

Does the web interface work? On occasion I've had a problem where guacd doesn't start properly or won't respond. The result is that no connections work. Restarting the docker container has always fixed it for me.

Yeah, that would do it. Glad you figured out the problem.