Hello Thank you for attention to my problem. I get from log you pointed after clean installation and first attempt to login as guacadmin:
17:45:52.104 [http-nio-8080-exec-12] WARN o.a.g.e.AuthenticationProviderFacade - The "mysql" authentication provider has encountered an internal error which will halt the authentication process. If this is unexpected or you are the developer of this authentication provider, you may wish to enable debug-level logging. If this is expected and you wish to ignore such failures in the future, please set "skip-if-unavailable: mysql" within your guacamole.properties. 17:45:52.105 [http-nio-8080-exec-12] ERROR o.a.g.rest.RESTExceptionMapper - Unexpected internal error: ### Error querying database. Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure With clean installation ( and update as well ) with image reverting back to 1.4.0 all work well. No compatibility! Any idea? Alexandre On Wed, 2023-02-22 at 11:01 -0500, Nick Couchman wrote: > On Wed, Feb 22, 2023 at 9:22 AM Alexandre Roumiantsev > <[email protected]> wrote: > > > > Hello > > > > I am using podman based guacamole long time on my RHEL system. Does > > not > > remember exectly with which version I have started. But latest > > version > > I have checked is 1.4.0 > > Today I have updated my server and found that clients could not > > access > > it(internal error), however I does not see any problem at server's > > side. > > I try to do both update and clean installation - same result. In > > both > > case 1.4.0 works well and 1.5.0 fails > > I use https://github.com/chadgeary/guacamole playbook for my > > installation > > > > You'll need to look at the container logs for guacamole-client and > see > what is causing the failures. > > -Nick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
signature.asc
Description: This is a digitally signed message part
