Taddeusz

@glidekirkland I just pushed a new version that you can try to see if that fixes your issue. Basically I added the "-s" switch to tini to fix that message. I'm not making it latest yet, jasonbean/guacamole:1.2.0-1

You're not running on Unraid? I've never tested on any other platform so I'm unsure how it would behave. Technically there's no reason it shouldn't be able to run on another platform. However, I'm not set up to test on any other platform.

@glidekirkland How are you editing your guacamole.config file? If it's a Windows tool like Notepad it may be replacing all the line endings with the incorrect ones. (LF vs CRLF). I've never seen your issue in my testing so I can only assume it has something to do with how you're editing or what you're adding to the config file.

I don’t believe there’s currently any way to do this. Their TOTP system is rather limited as it also doesn’t provide any means of backup codes. In the past what I’ve done is cleared the associated database columns to first disable TOTP for the user.

What is the error you’re getting in your browser?

@2Piececombo Are Swag and Guacamole on a custom network?

In your Swag appdata. nginx/proxy-confs/guacamole.subdomain.conf

Since you’re now getting a 502 message from Cloudflare I would recommend renaming the container from “ApacheGuacamole” to just “guacamole” and then make sure that’s the name used in your conf file.

You also won’t be able to connect directly to your Unraid server SSH with Guacamole on proxynet.

To use proxynet the name needs to be all lowercase and use that in the proxy conf file. That being said, I think you might have problems connecting to VM’s, if you use them, with Guacamole on proxynet. That’s the reason mine runs on br0.

That means your reverse proxy isn’t working. As far as I know the Docker DNS that Swag uses only works for a custom network type. Not for br0. On mine I had to point it to my Unraid server’s IP address and Guacamole port.

I don’t know. It’s either that or you mistyped your domain name in the address bar. Only way Chrome would give you that specific error.

It’s definitely not an issue specific to this Docker container. Something is wrong with your DNS if that’s the error you’re getting.

@stFfn The error you’re getting has to do with DNS. It stands for “non-existent domain”. Somewhere it’s misconfigured. I would recommend trying with a CNAME and point to your primary A record. In fact, for my domain I use Cloudflare. All my hostnames are CNAME to my primary A record which gets updated when my IP changes. It is my only A record.

Is guacamole registered as a CNAME in Cloudflare?

Did you modify the dns-conf/cloudflare.ini with your correct information?

Do you have other services you are passing through? If so, are they working?

What web browser are you using? You need to make sure that websockets are being proxied correctly. You can look in the Tomcat logs to check or if you’re using Chrome through the developer tools.

That’s just the description, what does the dialog look like?

I've personally never used the WOL functionality and don't have a way to test it. It looks like the Guacamole container needs to be in bridge mode for WOL to work correctly.

I will look into it. This is already a pretty huge container. While I do sympathize with your situation, given its size I'm hesitant to add more functionality that isn't core to Guacamole and can be provided another way.

Are you using the letsencrypt docker for reverse proxy? It includes fail2ban and has a filter for Guacamole. It’s possible the filter needs updated for your configuration.

For Guacamole's VNC file transfer to work it's going to need to be able to talk to the remote directly. This won't be possible with your virtual network configuration and I don't know how to work around that. I need to be able to access my VM's directly so I don't have it configured that way.

You would need to be running an SFTP server on your Windows VM for that to work.

I'm not sure how to get this set up. I installed the container. It had an error the first go and stopped. I restarted the container and now I can get a login screen but how to I login to manage it?