Taddeusz

I wasn't aware of this. It appears the documentation is spread out but here's where it explains it better: https://guacamole.apache.org/doc/gug/administration.html#idm140500640336672. Basically it looks like in the connection list in settings you hit the "+" next to the connection on which you want to allow sharing and click "New Sharing Profile".

The RDP and TLS encryption types are now considered legacy as NLA was introduced with Windows Vista. If you're connecting to a Windows machine there's actually a checkbox in the RDP settings to only allow connections via NLA. I believe it's defaulted to checked as that is the most secure connection type.

According to the log it defaults to RDP encryption if none is specified. At least on Windows 10 if I manually select "RDP encryption" or "TLS encryption" it won't connect. I have to select "Any" or "NLA (Network Level Authentication)" for it to connect.

@kasper219 Try selecting "Any" on "Security mode". If that is left unset on my Windows 10 vm it gives the same error.

@kasper219 Just got back from vacation. Have you been able to figure this out or is it still a problem?

I think you can modify your guacamole.properties file and change the logging level for guacd. That is really the only pertinent log here since it is what is making the connection. Did you double check and ensure you have Remote Desktop enabled? Is this Windows Professional?

Something is going on with your local network if unRAID can’t ping that address. Is your unRAID server on the same subnet as the computer you’re trying to connect to?

Do you have your Docker set to run on a macvlan?

Are you able to ping that IP address from your unRAID server?

Check “Ignore Server Certificate”.

@kasper219 Try putting 3389 in the port number.

I’ve had this happen too when connecting to certain Linux distributions. I’m not sure why it happens. It’s a TLS communication issue between guacd and whatever VNC you’re connecting to. I’ve reported the issue through Apache. They at least know about it. BTW, it also affects their own guacd Docker.

I'm glad you got it figured out. That feature is one of the things that annoys me. I wish there was an option to disable the single connection autoconnect.

Make sure you go in the settings and make sure "privileged" is enabled.

I've updated the image so that all the Tomcat logs get output to the guacamole/log folder. Previously it was only the catalina.out file.

I've updated the template to make it a privileged container. Tomcat apparently needs this for it to run correctly. I've also updated the image to show more detailed debugging information and prevent the database from being created if the guacamole.properties file doesn't exist.

For some reason starting the tomcat service always gives that "failed" message. I haven't been able to figure out why it does that. What does your catalina.out look like? It should be located in ApacheGucamole/guacamole/log.

Make very sure you are on the latest tag: jasonbean/guacamole:latest

I’m sorry this has happened and sorry to be blunt but are you going to give me something to work with? I can’t help you if you don’t provide me with logs. If you’re worried about privacy then sanitize them or send them to me privately but continuing to tell me over and over that it doesn’t work does nothing. I can tell you from a clean installation it works fine on my end. My production installation has worked fine this whole time. I have nothing to work from and can’t help if you don’t provide me with information. I assume you are on unRAID and checking for updates to make sure you have the latest built image.

You need a completely clean app data folder because the database password that is generated in the guacamole.properties file won’t match what the database creation script attempted to use.

Is this from a completely clean appdata folder?

Can I see your logs please. Both Docker and catalina.out.

Ok, I finally really figured this out. Apparently when I split this to create a multi-stage build I inadvertently removed the line that made firstrun.sh executable. I have corrected the error and pushed a new build.

Yes, there's a new build up as of an hour ago.

I apologize for the problems. This time it's really fixed. Tomcat was really not starting when the /config/guacamole/log folder didn't exist. I had to change the point at which that folder was being created.