In my environment I used guacamole server is 1.2.0 and client is 1.0.0.
From: Nick Couchman <[email protected]> Sent: Wednesday, January 27, 2021 9:41 PM To: [email protected] Subject: Re: Issue when connecting to guacamole server 1.2.0 On Wed, Jan 27, 2021 at 10:12 AM <[email protected] <mailto:[email protected]> > wrote: Jan 27 20:40:53 drapp1 server: 20:40:53.166 [http-bio-6698-exec-5] WARN o.a.g.r.auth.AuthenticationService - Authentication attempt from 192.168.90.47 for user "v2" failed. Having the timestamp doesn't provide any more of the information I was asking for. What about other logs around this? What about startup logs? Look at the following things, and post more information if you require assistance: 1) Has the MySQL Authentication Extension actually been loaded by Guacamole Client? There should be messages during startup of the Guacamole web application about what authentication extensions are loaded. 2) Can the MySQL Authentication Extension actually communicate correctly with the database? Are there any errors in the logs that indicate if it's having trouble talking to the DB, or is communicating successfully with the DB? 3) Is this the only user that fails, or do any attempts to log in with DB users fail? Usually the "guacadmin" user is the first one that gets added to the database, and is the one you use to log in and set up other accounts. Does guacadmin work, or is it failing, as well? 4) If guacadmin works and this is the only user failing log in, have you tried logging in with guacadmin and resetting this account's password? Have you tried different values for resetting the password to make sure that it is being typed correctly, it isn't running into an issue with unsupported characters, etc.? 5) If guacadmin - or any users in the DB at all - are not able to log in, then make sure that the MySQL extension is in the proper place, that the MySQL driver JAR file is loaded, that you've initialized the database correctly, etc. You have to be much, much, much, much more detailed in your questions, what you've tried, the errors or log messages you're getting, etc., in order for us to help you resolve this issue. As you can see from the list of questions above, there are many things to investigate that can help indicate where the issue may be, but as none of us has access to your environment, you're going to have to do that investigation yourself and provide us the details that will help point you in the right direction. -Nick
