Re: Problem with update from 1.4.0 to 1.5.0

Thank for attention to issue Alexandre On Sat, 2023-04-15 at 09:23 -0700, Michael Jumper wrote: > The nightly rebuild job was still pointing at the 1.5.0 source. I've > updated the build to point at 1.5.1 and triggered a manual rebuild. > The "*:latest" tag in Docker should be corrected in a

Re: Problem with update from 1.4.0 to 1.5.0

The nightly rebuild job was still pointing at the 1.5.0 source. I've updated the build to point at 1.5.1 and triggered a manual rebuild. The "*:latest" tag in Docker should be corrected in a few minutes. - Mike On Sat, Apr 15, 2023 at 9:15 AM Alexandre Roumiantsev wrote: > > Hello > > If I use

Re: Problem with update from 1.4.0 to 1.5.0

Hello If I use docker.io/guacamole/guacamole:1.5.1 and docker.io/guacamole/guacd:1.5.1 images then my upgrade is successful. If I use docker.io/guacamole/guacamole:latest and docker.io/guacamole/guacd:latest images then my upgrade is unsuccessful. I get same error messages in log as I get with

Re: Problem with update from 1.4.0 to 1.5.0

On Sat, Apr 15, 2023 at 2:57 AM Alexandre Roumiantsev wrote: > > Thank for info > > I have checked new release and it really solve the problem with > upgrading from 1.4.0 to 1.5.0 ( > https://lists.apache.org/thread/jg4s21f3kotqvbnvqqhvdqcsdr88zwwh ). > Upgrade from 1.4.0 to 1.5.1 successfully. >

Re: Problem with update from 1.4.0 to 1.5.0

Thank for info I have checked new release and it really solve the problem with upgrading from 1.4.0 to 1.5.0 ( https://lists.apache.org/thread/jg4s21f3kotqvbnvqqhvdqcsdr88zwwh ). Upgrade from 1.4.0 to 1.5.1 successfully. However, one question: why latest still has problem with upgrading? It

Re: Re: Problem with update from 1.4.0 to 1.5.0

On Fri, Mar 3, 2023 at 11:19 AM Alexandre Roumiantsev wrote: > Hello > > It was announced about some changes: > [image: vnick] Nick Couchman > added > a comment - 03/Mar/23 14:08 >

Re: Problem with update from 1.4.0 to 1.5.0

I was having some very similar errors. I went down the same path with SSL certs and the whole time the issue was Tomcat 10. After some advice I changed back to Tomcat 9 and all of those errors resolved.On Mar 3, 2023, at 11:18 AM, Alexandre Roumiantsev wrote:HelloIt was announced about some

Re: Re: Problem with update from 1.4.0 to 1.5.0

Hello It was announced about some changes: vnick Nick Couchman added a comment - 03/Mar/23 14:08 MySQL Connector/J has been updated. However I does not see any changes. No success with 1.5.0. I see same problem. Does somebody have success with container version 1.5.0 guacamole? Alexandre  On

Re: Re: Problem with update from 1.4.0 to 1.5.0

Hello Thank you Sebastian and Sander. Now I understand the problem. I agree with Sebastian about the 1.4.0 and 1.5.0 version differences regarding guacamole related jdbc connections. This is a big headache for me Best regards, Alexandre On Thu, 2023-02-23 at 06:57 +, Sebastian Männling

Re: Re: Problem with update from 1.4.0 to 1.5.0

Hi Alexandre, No didn't have that error. My MYSQL Server (Percona to be exact) is using SSL but without any CA. Perhaps that is the issue on MySQL side. Sander. Op do, 23 feb 2023 07:44:59 +0100 schreef Alexandre Roumiantsev Hello Thanks

Re: Re: Problem with update from 1.4.0 to 1.5.0

Hi, probably I ran into the same (or at least a similar) issue… I ended up with creating a self signed cert for the MySQL container and adding the self signing CA to guacamoles Java trust store… After that guacamole was able to communicate properly with the database. To me it looks like 1.5.0

Re: Re: Problem with update from 1.4.0 to 1.5.0

Hello Thanks Sander. You pointed me to problematic place. However after adding  " -e MYSQL_SSL_MODE=disabled" I get problem some deeper: 06:33:09.618 [http-nio-8080-exec-6] WARN o.a.g.e.AuthenticationProviderFacade - The "mysql" authentication provider has encountered an internal error which will

RE: Re: Problem with update from 1.4.0 to 1.5.0

Hi Alexandre, Encountered the same issue today after upgrading Docker container. Downgraded to 1.4.0 got a better error message warning me for unsecured connection to MySQL. Wed Feb 22 20:50:49 CET 2023 WARN: Establishing SSL connection without server's identity verification is not

Re: Problem with update from 1.4.0 to 1.5.0

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

Re: Problem with update from 1.4.0 to 1.5.0

On Wed, Feb 22, 2023 at 9:22 AM Alexandre Roumiantsev 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

Problem with update from 1.4.0 to 1.5.0

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