Taddeusz

@Zeroeth I've got a small update on the RDP printing issue. They've figured out what is causing the problem. They've changed the status to "in progress". Not sure when the fix will be made or what version it will be implemented in. They downgraded the priority to "minor" but since this affects everyone's ability to print I would hope it makes it into 1.5.1. BTW, here is the JIRA issue: https://issues.apache.org/jira/browse/GUACAMOLE-1755

T-Mobile uses IPv6 and our home ISP uses IPv4. When I connect a device through my phone's hotspot that uses an IPv4 NAT the WireGuard VPN connection works fine. When I try to connect to the VPN straight from my phone the server doesn't receive any traffic. Is there any way to fix this? I seem to remember I had the same problem when I was using OpenVPN but I was able to work around it somehow. Any ideas?

@bombz Yes, moving forward you should be fine now. There are some problems with the 1.5.0 version of VNC support that makes it impossible to connect to a host that requires a password. That should be corrected by the upcoming 1.5.1 release. Not sure when that will happen though.

@bombz I'm glad you got the upgrade working. While I was testing 1.5.0 the base container changed from Debian to Alpine. Debian used an older version of MariaDB and I came to realize the 1.4.0 container wasn't shutting it down correctly so I had to push an update of the 1.4.0 to correct this and then wait a few days before I released the 1.5.0 container to try and reduce the number of people having issues with the upgrade. The result of MariaDB not shutting down correctly before upgrading was that the database was left in a bad state and needed to be started back up in the old version of MariaDB and then shut down correctly before it could be read properly by the newer server version. I hope that makes things more clear for the community.

@bombz In your guacamole.properties (sorry, previously I had the incorrect filename) file you should have settings that appear somewhat like the following: ### http://guacamole.apache.org/doc/gug/jdbc-auth.html#jdbc-auth-mysql ### MySQL properties mysql-hostname: 127.0.0.1 mysql-port: 3306 mysql-database: guacamole mysql-username: guacamole mysql-password: <password> By default mysql-hostname is set to 127.0.0.1. If you want to use an eternal database instance you would change that to match the correct address. If the mysql-hostname setting is NOT set to 127.0.0.1 in your properties file and you're 100% certain you're using an external database instance you can change your container to the latest-nomariadb. Personally that's how I have mine set because I DO use a separate MariaDB Docker container for multiple applications instead of having an assortment of separate databases. To be sure, Guacamole requires a database of SOME kind even if it is using the default authentication of the user-mapping.xml file. Unlike the official Guacamole containers my container packages both the Guacamole server (guacd), the Guacamole client (using Tomcat), and MariaDB as the default authentication method. You are certainly welcome to use your own database instance which can be MySQL/MariaDB, PostgreSQL, Microsoft SQL Server, or the default user-mapping.xml file. Or a combination such as LDAP/Active Directory, SAML, or OpenID for the actual authentication plus some sort of database to store user and connection data. Again, look at your container's guacamole.properties file to determine how your container is configured. If you're using Unraid it should be located in appdata/ApacheGuacamole/guacamole/guacamole.properties.

If you’re not using the included MariaDB/MySQL then what are you using to store the Guacamole data? Do you have the MySQL settings in your guacamole.config file commented out?

@bombz You say you're not using MariaDB but you obviously have OPT_MYSQL set to "Y" in your configuration because it would not attempt to install the MySQL extension otherwise. MariaDB is essentially equivalent to and a drop-in replacement for MySQL. What I would recommend is downgrading to the 1.4.0-3 release and then upgrade back to latest.

@Kamvas Did you not see that I said this is a problem that’s going to get fixed with 1.5.1? Sorry it’s affecting you but I can’t really do anything but wait till they release the fix.

@3dee I think there are registry settings to force RDP to use TLS 1.0/1.1 but I would consider that really the last thing you want to do if security is that important. It shouldn't be that huge of a problem if this computer is not directly on the internet.

@3dee I don't know German and I don't remember what those options were. Maybe change the Security Mode in Guacamole from NLA to RDP encryption or last resort "Any".

@3dee I'm not entirely sure but at this time it looks like your only option may be to disable NLA on your Windows 7 machine.

@3dee Also, if you add the environment variable GUACD_LOG_LEVEL and set the value to "debug" without the quotes the output will be more detailed.

@3dee Sorry, I missed that. I wonder if since Windows 7 is end-of-life that means it won't also have its CA certificates updated? Meaning any certificates will forever be untrusted. Can you connect to that machine from another Windows machine? You might also look in the Windows logs to see if it shines any light on why it's not connecting.

@3dee In the RDP connection settings there's an option, "Ignore server certificate", make sure it's checked.

Looks like it's going to be fixed in 1.5.1. In their JIRA it's reported in GUACAMOLE-1741. It appears it's an incompatibility with the OpenSSL library so I hope the fix won't affect SSH.

@Urbanpixels @FabienN @Kamvas I installed TightVNC server on my Windows 11 VM. I was able to connect to it through the Real VNC Viewer just fine so I know it was working. I started the VNC server with no password required. In Guacamole if I created the connection with NO port specified (blank port input box) it will not connect. It doesn't seem to assume port 5900 if no port is specified. If I specify port 5900 in the connection settings it successfully connects. I also did this test on 1.4.0 but have the same problem. If I don't specify a port it won't connect. I'm not sure if this was able to reproduce your problem. I think the only thing I can say is to make sure both the IP and port are specified in the connection settings. I've been able to connect to any VNC server if I specify the port.

What OS’s are these connections to?

@Urbanpixels Is this a newly created connection or one that was created before upgrading and stopped working? Make sure the connection information is in the correct box, that it’s not in the Guacamole Proxy Parameters section.

@nik82 I've just pushed a small update. There was a guacd dependency I missed. I've not had any problems with VNC connections. The ones I've tried are to Docker containers.

@nik82 Are there any errors in the log?

@Zeroeth I've tested with their guacd container and get the same error. In fact, it's actually worse because once GhostScript fails once it apparently never closes the print job and I end up with an error in my remote Windows which I wasn't getting from my own guacd. I'll put in a bug report if there isn't one already.

@Zeroeth I've reproduced the problem. I'll have to do some testing to see if it's a bug with guacd or with my implementation.

Ok, I have promoted 1.5.0 to be "latest". Please be aware of the big red message at the top. You MUST have upgraded to 1.4.0-3 before upgrading to 1.5.0.

@codyrat I would suggest making a comment and asking if they could push the change to 1.5.1.

@codyrat I'm sorry, I take the guacamole server (guacd) binary as it is. It would take a lot of work to make a custom build to back port that one fix. I know that report says that the fix version will be 1.6.0 but it appears that they are going to do a 1.5.1 release. The change was merged 2 hours ago.