You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Henri Alves de Godoy <he...@fca.unicamp.br> on 2022/01/26 12:54:08 UTC

After Upgrade Guacamole 1.3 --> 1.4

Hi, could someone help me

After upgrading to 1.4 the following error appears

The guaca client .war and the server have been updated.

Jan 26 09:50:16 remoto guacd[1925]: Guacamole protocol violation. Perhaps
the version of guacamole-client is incompatible with this version of guacd?
Jan 26 09:50:16 remoto server: 09:50:16.777 [https-openssl-nio-8443-exec-5]
ERROR o.a.g.s.GuacamoleHTTPTunnelServlet - HTTP tunnel request failed:
javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake


Jan 26 09:49:46 remoto systemd: Starting LSB: Guacamole proxy daemon...
Jan 26 09:49:46 remoto guacd[1923]: Guacamole proxy daemon (guacd) version
1.4.0 started
Jan 26 09:49:46 remoto guacd: Starting guacd: guacd[1923]:
INFO:#011Guacamole proxy daemon (guacd) version 1.4.0 started
Jan 26 09:49:46 remoto guacd: SUCCESS
Jan 26 09:49:46 remoto guacd[1925]: Listening on host 127.0.0.1, port 4822
Jan 26 09:49:46 remoto systemd: Started LSB: Guacamole proxy daemon.


Did I forget something?

Thanks

--

Re: After Upgrade Guacamole 1.3 --> 1.4

Posted by Henri Alves de Godoy <he...@fca.unicamp.br>.
Hi Nick,

I downloaded from git hub first.

Then I get the tar.gz and did the compilation.

Something happened that removed the conf from my guacd.service and removed
the SSL keys information options. I hadn't noticed.

That was the reason and in this case of my first email, I was able to find
the problem.

But when trying to use it, I noticed the various problems that I reported
in my second email.

Thanks
Henri


Em qua., 26 de jan. de 2022 às 16:24, Nick Couchman <vn...@apache.org>
escreveu:

> On Wed, Jan 26, 2022 at 7:56 AM Henri Alves de Godoy <
> henri.godoy@fca.unicamp.br> wrote:
>
>> Hi, could someone help me
>>
>> After upgrading to 1.4 the following error appears
>>
>> The guaca client .war and the server have been updated.
>>
>> Jan 26 09:50:16 remoto guacd[1925]: Guacamole protocol violation. Perhaps
>> the version of guacamole-client is incompatible with this version of guacd?
>> Jan 26 09:50:16 remoto server: 09:50:16.777
>> [https-openssl-nio-8443-exec-5] ERROR o.a.g.s.GuacamoleHTTPTunnelServlet -
>> HTTP tunnel request failed: javax.net.ssl.SSLHandshakeException: Remote
>> host terminated the handshake
>>
>>
> I replied to your other thread, but these messages indicate some
> communication issue between the guacd and guacamole client. The fact that
> you're seeing this when running them both on the same system is very odd.
> Among the things that I'd look at are any security software that might be
> mangling the communication - either A/V software on the Linux system, or a
> Web Application Firewall or Deep Packet Inspection firewall that could be
> blocking something.
>
> Have you modified the code at all - any changes to the server or client?
> Or are you just deploying what you've downloaded from the web site?
>
> -NIck
>


--

Re: After Upgrade Guacamole 1.3 --> 1.4

Posted by Nick Couchman <vn...@apache.org>.
On Wed, Jan 26, 2022 at 7:56 AM Henri Alves de Godoy <
henri.godoy@fca.unicamp.br> wrote:

> Hi, could someone help me
>
> After upgrading to 1.4 the following error appears
>
> The guaca client .war and the server have been updated.
>
> Jan 26 09:50:16 remoto guacd[1925]: Guacamole protocol violation. Perhaps
> the version of guacamole-client is incompatible with this version of guacd?
> Jan 26 09:50:16 remoto server: 09:50:16.777
> [https-openssl-nio-8443-exec-5] ERROR o.a.g.s.GuacamoleHTTPTunnelServlet -
> HTTP tunnel request failed: javax.net.ssl.SSLHandshakeException: Remote
> host terminated the handshake
>
>
I replied to your other thread, but these messages indicate some
communication issue between the guacd and guacamole client. The fact that
you're seeing this when running them both on the same system is very odd.
Among the things that I'd look at are any security software that might be
mangling the communication - either A/V software on the Linux system, or a
Web Application Firewall or Deep Packet Inspection firewall that could be
blocking something.

Have you modified the code at all - any changes to the server or client? Or
are you just deploying what you've downloaded from the web site?

-NIck