James Freeman created GUACAMOLE-1747:
----------------------------------------
Summary: VNC Connections not working after upgrade to 1.5.0
(docker official images)
Key: GUACAMOLE-1747
URL: https://issues.apache.org/jira/browse/GUACAMOLE-1747
Project: Guacamole
Issue Type: Bug
Components: guacd-docker
Affects Versions: 1.5.0
Environment: Docker version 23.0.1, build a5ee5b1 (CE)
on Ubuntu Server 22.04 LTS
Reporter: James Freeman
Hi there
I have been running Guacamole in the official Docker containers since version
1.4.0, and it has always been rock solid. I recently upgraded to the new
release of 1.5.0 as I wanted the new SSH support available to connect to my
Ubuntu 22.04 hosts without reconfiguring them.
Since the upgrade, the RDP and SSH connections work perfectly, but VNC
connections (which previously worked in 1.4.0) no longer work. I have confirmed
I can still connect using a normal VNC viewer without issue, so am confident in
the VNC server operation and password. In the guacd container logs, I see:
{code:java}
[email protected] | guacd[1]: INFO:
Creating new client for protocol "vnc"
[email protected] | guacd[1]: INFO:
Connection ID is
"$ea4c4e82-84b6-4c75-a9cb-b7db83296955"[email protected]
| guacd[2099]: DEBUG: Processing instruction: size
[email protected]
| guacd[2099]: DEBUG: Processing instruction: audio
[email protected]
| guacd[2099]: DEBUG: Processing instruction: video
[email protected] | guacd[2099]: DEBUG:
Processing instruction: image
[email protected] | guacd[2099]: DEBUG:
Processing instruction: timezone
[email protected] | guacd[2099]: DEBUG:
Processing instruction: name
[email protected] | guacd[2099]: INFO:
Cursor rendering: local
[email protected] | guacd[2099]: DEBUG:
Parameter "swap-red-blue" omitted. Using default value of
[email protected] | guacd[2099]:
DEBUG: Parameter "read-only" omitted. Using default value of
[email protected] | guacd[2099]:
DEBUG: Parameter "color-depth" omitted. Using default value of 0.
[email protected] |
guacd[2099]: DEBUG: Parameter "force-lossless" omitted. Using default
value of 0.
[email protected] | guacd[2099]: DEBUG:
Parameter "dest-port" omitted. Using default value of
[email protected] | guacd[2099]:
DEBUG: Parameter "encodings" omitted. Using default value of "zrle ultra
copyrect hextile zlib corre rre raw".
[email protected] | guacd[2099]: DEBUG:
Parameter "autoretry" omitted. Using default value of
[email protected] | guacd[2099]:
DEBUG: Parameter "reverse-connect" omitted. Using default value of 0.
[email protected] |
guacd[2099]: DEBUG: Parameter "listen-timeout" omitted. Using default
value of 5000.
[email protected] | guacd[2099]: DEBUG:
Parameter "enable-audio" omitted. Using default value of
[email protected] | guacd[2099]:
DEBUG: Parameter "enable-sftp" omitted. Using default value of 0.
[email protected] |
guacd[2099]: DEBUG: Parameter "sftp-hostname" omitted. Using default value
of "vnchost.example.com".
[email protected] | guacd[2099]: DEBUG:
Parameter "sftp-port" omitted. Using default value of
"22"[email protected] | guacd[2099]:
DEBUG: Parameter "sftp-username" omitted. Using default value of
""[email protected] | guacd[2099]:
DEBUG: Parameter "sftp-password" omitted. Using default value of
""[email protected] | guacd[2099]:
DEBUG: Parameter "sftp-root-directory" omitted. Using default value of
"/"[email protected] | guacd[2099]:
DEBUG: Parameter "sftp-server-alive-interval" omitted. Using default value
of [email protected] | guacd[2099]:
DEBUG: Parameter "sftp-disable-download" omitted. Using default value of
[email protected] | guacd[2099]:
DEBUG: Parameter "sftp-disable-upload" omitted. Using default value of
[email protected] | guacd[2099]:
DEBUG: Parameter "recording-name" omitted. Using default value of
"recording"[email protected] |
guacd[2099]: DEBUG: Parameter "recording-exclude-output" omitted. Using
default value of [email protected] |
guacd[2099]: DEBUG: Parameter "recording-exclude-mouse" omitted. Using
default value of [email protected] |
guacd[2099]: DEBUG: Parameter "recording-include-keys" omitted. Using
default value of [email protected] |
guacd[2099]: DEBUG: Parameter "create-recording-path" omitted. Using
default value of [email protected] |
guacd[2099]: DEBUG: Parameter "disable-copy" omitted. Using default value
of [email protected] | guacd[2099]:
DEBUG: Parameter "disable-paste" omitted. Using default value of
[email protected] | guacd[2099]:
DEBUG: Parameter "wol-send-packet" omitted. Using default value of
[email protected] | guacd[2099]: INFO:
User "@b7c484d3-73af-4ede-9f9a-7bac10aa319a" joined connection
"$ea4c4e82-84b6-4c75-a9cb-b7db83296955" (1 users now
present)[email protected] | guacd[2099]:
DEBUG: Client is using protocol version
"VERSION_1_5_0"[email protected] |
guacd[2099]: ERROR: Unable to connect to VNC
[email protected] | guacd[2099]:
INFO: User "@b7c484d3-73af-4ede-9f9a-7bac10aa319a" disconnected (0 users
remain)[email protected] | guacd[2099]:
INFO: Last user of connection "$ea4c4e82-84b6-4c75-a9cb-b7db83296955"
disconnectedguacamole_guacd.1.3vb2g62mj...@docknode01.example.com |
guacd[2099]: DEBUG: Requesting termination of
[email protected] |
guacd[2099]: DEBUG: Client terminated
successfully.guacamole_guacd.1.3vb2g62mj...@docknode01.example.com |
guacd[1]: INFO: Connection "$ea4c4e82-84b6-4c75-a9cb-b7db83296955"
[email protected] | guacd[1]:
DEBUG: Guacamole connection closed during
[email protected] | guacd[1]:
DEBUG: Error reading "select": End of stream reached while reading instruction
{code}
The VNC server is running as follows:
{code:java}
user 868815 868814 0 Mar03 ? 00:00:01 /usr/bin/Xtigervnc :10
-NeverShared=0 -AlwaysShared=1 -localhost=0 -desktop vnchost.example.com:10
(jamesf_local) -rfbport 5910 -PasswordFile /pool01/home/user/.vnc/passwd
-SecurityTypes VncAuth,TLSVnc -auth /pool01/home/user/.Xauthority -geometry
1440x900 -depth 24 {code}
Nothing of note appears in the VNC server logs.
I tried using Wireshark to sniff the traffic between the Docker host and the
VNC host - I see some negotiation going on between the two hosts (but am unsure
how to decode the protocol), and then the connection is reset.
Please let me know what additional information I can provide to help debug this
issue. I'm not sure where to look next - I've double checked all configuration,
and it worked fine in 1.4.0, so it feels like something has changed but I can't
figure out what.
Thanks in advance!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
