Taddeusz

1.5.1 has been released. It also looks like there's going to be a 1.5.2. With this release I've simplified the build. Instead of building the client myself I discovered that I no longer need to do that so I'm just pulling down both of their server and client images.

@Hugh Jazz What version of MariaDB are you running? I'm also running the linuxserver MariaDB container. Mine is 10.6.12 and my server checks for updates nightly. If you have MySQL Workbench or run a query from the CLI execute the following and it will give you the version of your instance: SELECT @@version;

They updated the version of the MySQL Connector they were using. It caused me some confusion for a while switching back and forth between my "production" version of 1.5.0 and my test version of 1.5.1-RC1. I'm not really sure what's going on. Can you please send a catalina.out file from 1.5.1-RC1?

@Hugh Jazz Are you using MariaDB or MySQL as your database instance?

@Hugh Jazz I'm looking at your catalina.out files a little bit further and I noticed it says it's having trouble connecting to the mysql server with SSL but SSL is not enabled on the server. This is apparently a problem that has been fixed with 1.5.1: https://issues.apache.org/jira/browse/GUACAMOLE-1738?jql=project %3D GUACAMOLE AND text ~ "mysql ssl" You might give 1.5.1-RC1 another try.

What files are in your guacamole/lib folder? I'm thinking the lib files aren't being updated properly but I need more confirmation.

On what version did you start using Guacamole? Since you're using an external MySQL or MariaDB instance it's up to you to upgrade the database schema. It's been a while since they've changed the schema (~5 years) but if you started using it prior to 1.0.0 and haven't upgraded the schema it's possible that's causing a problem.

I'm not sure what's going on. There's just nothing in that log. I see the same OpenSSL error in my own log but I'm not having any issues. I am also using the one without MariaDB using an external MariaDB Docker container. Are you using any other authentication method like OpenID or SAML?

Is it before or after you're logging in? From the log file it appears authentication is successful. I don't see any obvious problems. This is a log from 1.5.0 right?

@Hugh Jazz When do you receive this error?

If it's not easy to scrub the information you may DM it to me if you're more comfortable with that. The whole file would be more helpful since it's not always obvious where the error is occurring.

FYI, 1.5.1-RC1 includes changes to fix the VNC with password problem and RDP printing among a few other problems.

For anyone who wants it or needs it I've uploaded 1.5.1-RC1. Change to jasonbean/guacamole:1.5.1-RC1 or jasonbean/guacamole:1.5.1-RC1-nomariadb if you'd like to try it out. Once 1.5.1 becomes final I will promote that one to "latest".

@Hugh Jazz You should look at the tomcat log, catalina.out file.

@Zeroeth It's now been marked as fixed and closed to be included in 1.5.1!

@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".