noVNC failing on Ubuntu 24.04.1, works on Ubuntu 22.04.5

[Richard Mixon]

We are upgrading our systems to Ubuntu 24.04.1 (latest point release) - but it seems noVNC fails.  I'm including the ~/.vnc/host:1.log file from each along with release info.

Ubuntu 22.04.5 - this works

n2kowner@host:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.5 LTS"

n2kowner@host:~$ cat ~/.vnc/host\:1.log
TurboVNC Server (Xvnc) 64-bit v3.1.2 (build 20240808)
Copyright (C) 1999-2024 The VirtualGL Project and many others (see README.md)
Visit http://www.TurboVNC.org for more information on TurboVNC

06/11/2024 18:54:12 Using security configuration file /etc/turbovncserver-security.conf
06/11/2024 18:54:12 Enabled security type 'tlsvnc'
06/11/2024 18:54:12 Enabled security type 'tlsotp'
06/11/2024 18:54:12 Enabled security type 'tlsplain'
06/11/2024 18:54:12 Enabled security type 'x509vnc'
06/11/2024 18:54:12 Enabled security type 'x509otp'
06/11/2024 18:54:12 Enabled security type 'x509plain'
06/11/2024 18:54:12 Enabled security type 'vnc'
06/11/2024 18:54:12 Enabled security type 'otp'
06/11/2024 18:54:12 Enabled security type 'unixlogin'
06/11/2024 18:54:12 Enabled security type 'plain'
06/11/2024 18:54:12 Desktop name 'TurboVNC: host:1 (n2kowner)' (host:1)
06/11/2024 18:54:12 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
06/11/2024 18:54:12 Listening for VNC connections on TCP port 5901
06/11/2024 18:54:12 Interface 0.0.0.0
06/11/2024 18:54:12 Framebuffer: BGRX 8/8/8/8
06/11/2024 18:54:12 New desktop size: 1240 x 900
06/11/2024 18:54:12 New screen layout:
06/11/2024 18:54:12 0x00000040 (output 0x00000040): 1240x900+0+0
06/11/2024 18:54:12 Maximum clipboard transfer size: 1048576 bytes
06/11/2024 18:54:12 VNC extension running!
xstartup.turbovnc: Creating new session bus instance:
xstartup.turbovnc: unix:abstract=/tmp/dbus-jd0S2ZKbGE,guid=5925b7e74ad6bc21bad112f1672bbb55
xstartup.turbovnc: Using 'gnome-flashback-metacity' window manager in
xstartup.turbovnc: /usr/share/xsessions/gnome-flashback-metacity.desktop
xstartup.turbovnc: Executing /usr/bin/ssh-agent vglrun +wm /etc/X11/Xsession "/usr/libexec/gnome-flashback-metacity"
06/11/2024 18:54:17 New desktop size: 1240 x 900

06/11/2024 18:59:43 [1] Got connection from 127.0.0.1 on port 47014
06/11/2024 18:59:43 [1] Normal socket connection
06/11/2024 18:59:43 [1] Using protocol version 3.8
06/11/2024 18:59:43 [1] Enabling VeNCrypt protocol extensions
06/11/2024 18:59:43 [1] Client requested VeNCrypt sub-type 2
06/11/2024 18:59:43 [1] Full-control authentication enabled
06/11/2024 18:59:43 Number of connected clients: 1
06/11/2024 18:59:43 [1] Pixel format:
06/11/2024 18:59:43 [1] 32 bpp, depth 24, little endian
06/11/2024 18:59:43 [1] true colour: max r 255 g 255 b 255, shift r 0 g 8 b 16
06/11/2024 18:59:43 [1] Enabling CopyRect encoding
06/11/2024 18:59:43 [1] Using tight encoding
06/11/2024 18:59:43 [1] rfbProcessClientNormalMessage: ignoring unknown encoding -260 (fffffefc)
06/11/2024 18:59:43 [1] rfbProcessClientNormalMessage: ignoring unknown encoding 21 (15)
06/11/2024 18:59:43 [1] Using JPEG subsampling 0, Q79
06/11/2024 18:59:43 [1] Enabling Desktop Size protocol extension
06/11/2024 18:59:43 [1] Enabling LastRect protocol extension
06/11/2024 18:59:43 [1] Enabling QEMU Extended Key Event protocol extension
06/11/2024 18:59:43 [1] Enabling Extended Desktop Size protocol extension
06/11/2024 18:59:43 [1] rfbProcessClientNormalMessage: ignoring unknown encoding -309 (fffffecb)
06/11/2024 18:59:43 [1] Enabling Fence protocol extension
06/11/2024 18:59:43 [1] Enabling Continuous Updates protocol extension
06/11/2024 18:59:43 [1] rfbProcessClientNormalMessage: ignoring unknown encoding -307 (fffffecd)
06/11/2024 18:59:43 [1] Enabling Extended Clipboard protocol extension
06/11/2024 18:59:43 [1] rfbProcessClientNormalMessage: ignoring unknown encoding 1464686180 (574d5664)
06/11/2024 18:59:43 [1] Enabling full-color cursor updates
06/11/2024 18:59:43 [1] Using Tight compression level 2
06/11/2024 18:59:43 [1] WARNING: Disabling QEMU Extended Key Event extension because neither LED state
06/11/2024 18:59:43 [1] extension is supported by the client.
06/11/2024 18:59:43 Using 4 threads for Tight encoding
06/11/2024 18:59:43 [1] Client clipboard capabilities:
06/11/2024 18:59:43 [1] - Plain text (limit = 0 bytes)
06/11/2024 18:59:43 [1] Continuous updates enabled
06/11/2024 18:59:43 [1] Continuous updates enabled
n2kowner@host:~$

Ubuntu 24.04.1 - this fails

n2kowner@host:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04.1 LTS"

n2kowner@host:~$ cat ~/.vnc/host\:1.log
TurboVNC Server (Xvnc) 64-bit v3.1.2 (build 20240808)
Copyright (C) 1999-2024 The VirtualGL Project and many others (see README.md)
Visit http://www.TurboVNC.org for more information on TurboVNC

06/11/2024 19:06:01 Using security configuration file /etc/turbovncserver-security.conf
06/11/2024 19:06:01 Enabled security type 'tlsvnc'
06/11/2024 19:06:01 Enabled security type 'tlsotp'
06/11/2024 19:06:01 Enabled security type 'tlsplain'
06/11/2024 19:06:01 Enabled security type 'x509vnc'
06/11/2024 19:06:01 Enabled security type 'x509otp'
06/11/2024 19:06:01 Enabled security type 'x509plain'
06/11/2024 19:06:01 Enabled security type 'vnc'
06/11/2024 19:06:01 Enabled security type 'otp'
06/11/2024 19:06:01 Enabled security type 'unixlogin'
06/11/2024 19:06:01 Enabled security type 'plain'
06/11/2024 19:06:01 Desktop name 'TurboVNC: host:1 (n2kowner)' (host:1)
06/11/2024 19:06:01 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
06/11/2024 19:06:01 Listening for VNC connections on TCP port 5901
06/11/2024 19:06:01 Interface 0.0.0.0
06/11/2024 19:06:01 Framebuffer: BGRX 8/8/8/8
06/11/2024 19:06:01 New desktop size: 1240 x 900
06/11/2024 19:06:01 New screen layout:
06/11/2024 19:06:01 0x00000040 (output 0x00000040): 1240x900+0+0
06/11/2024 19:06:01 Maximum clipboard transfer size: 1048576 bytes
06/11/2024 19:06:01 VNC extension running!
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Could not resolve keysym XF86CameraAccessEnable
> Warning: Could not resolve keysym XF86CameraAccessDisable
> Warning: Could not resolve keysym XF86CameraAccessToggle
> Warning: Could not resolve keysym XF86NextElement
> Warning: Could not resolve keysym XF86PreviousElement
> Warning: Could not resolve keysym XF86AutopilotEngageToggle
> Warning: Could not resolve keysym XF86MarkWaypoint
> Warning: Could not resolve keysym XF86Sos
> Warning: Could not resolve keysym XF86NavChart
> Warning: Could not resolve keysym XF86FishingChart
> Warning: Could not resolve keysym XF86SingleRangeRadar
> Warning: Could not resolve keysym XF86DualRangeRadar
> Warning: Could not resolve keysym XF86RadarOverlay
> Warning: Could not resolve keysym XF86TraditionalSonar
> Warning: Could not resolve keysym XF86ClearvuSonar
> Warning: Could not resolve keysym XF86SidevuSonar
> Warning: Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
xstartup.turbovnc: Creating new session bus instance:
xstartup.turbovnc: unix:path=/tmp/dbus-E839ozOkxw,guid=c4e96d8cc8775a3adc5fe842672bbe1a
xstartup.turbovnc: Using 'gnome-flashback-metacity' window manager in
xstartup.turbovnc: /usr/share/xsessions/gnome-flashback-metacity.desktop
xstartup.turbovnc: Executing /usr/bin/ssh-agent vglrun +wm /etc/X11/Xsession "/usr/libexec/gnome-flashback-metacity"
n2kowner@host:~$

Thank you much - Richard Mixon

[Pierre Ossman]

On 07/11/2024 00:18, Richard Mixon wrote:
> We are upgrading our systems to Ubuntu 24.04.1 (latest point release) - but
> it seems noVNC fails. I'm including the ~/.vnc/host:1.log file from each
> along with release info.
>

In what way does it fail? Is it the VNC server that fails to start? That
is unfortunately not part of noVNC, so you'll need to ask the TurboVNC
community for assistance there.

Regards,
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[Richard Mixon]

Yes, it may be a TurboVNC issue, but please also consider these messages I found in /var/log/syslog that appear just after chronologically:

2024-11-06T19:04:05.803949+00:00 host novnc_proxy[918]: No installed websockify, attempting to clone websockify... 2024-11-06T19:04:05.827248+00:00 host novnc_proxy[930]: Cloning into '/home/n2kowner/noVNC-1.4.0/utils/websockify'... 2024-11-06T9:04:05.902497+00:00 host novnc_proxy[932]: fatal: unable to access 'https://github.com/novnc/websockify/': Could not resolve host: github.com

2024-11-06T19:04:05.910077+00:00 host novnc_proxy[918]: Unable to locate /home/n2kowner/noVNC-1.4.0/utils/websockify/run after downloading

It says it cannot reach github.com, but on the same host that is failing I can ping it fine:

n2kowner@host:/opt$ ping github.com
PING github.com (140.82.112.3) 56(84) bytes of data.
64 bytes from lb-140-82-112-3-iad.github.com (140.82.112.3): icmp_seq=1 ttl=252 time=82.6 ms
64 bytes from lb-140-82-112-3-iad.github.com (140.82.112.3): icmp_seq=2 ttl=252 time=82.7 ms

Is thi still not a noVNC issue?

Thank you much, as always - Richard

--

Richard Mixon

2209 E. Constance Way

Phoenix, AZ 85042

mobile: 480-577-6834

[Pierre Ossman]

On 07/11/2024 14:29, Richard Mixon wrote:
> Yes, it may be a TurboVNC issue, but please also consider these messages I
> found in /var/log/syslog that appear just after chronologically:
>
> 2024-11-06T19:04:05.803949+00:00 host novnc_proxy[918]: No installed
> websockify, attempting to clone websockify... 2024-11-06T19:04:05.827248+00:00
> host novnc_proxy[930]: Cloning into
> '/home/n2kowner/noVNC-1.4.0/utils/websockify'...
> 2024-11-06T9:04:05.902497+00:00 host novnc_proxy[932]: fatal: unable to
> access 'https://github.com/novnc/websockify/': Could not resolve host:
> github.com
> 2024-11-06T19:04:05.910077+00:00 host novnc_proxy[918]: Unable to locate
> /home/n2kowner/noVNC-1.4.0/utils/websockify/run after downloading
>
>
> It says it cannot reach github.com, but on the same host that is failing I
> can ping it fine:
>
> n2kowner@host:/opt$ ping github.com
> PING github.com (140.82.112.3) 56(84) bytes of data.
> 64 bytes from lb-140-82-112-3-iad.github.com (140.82.112.3): icmp_seq=1
> ttl=252 time=82.6 ms
> 64 bytes from lb-140-82-112-3-iad.github.com (140.82.112.3): icmp_seq=2
> ttl=252 time=82.7 ms
>
>
> Is thi still not a noVNC issue?
>

Probably not, given that there is some general network issue. But that's
also not a TurboVNC issue.

How is novnc_proxy called? Perhaps in some environment with limited
network settings?

[Richard Mixon]

novnc_proxy is called from service unit file /etc/systemd/system/noVNC.service. Here are the contents:

[Unit]
Description=Init file for noVNC 1.4.0 proxy
Documentation=
After=network.target auditd.service

[Service]
ConditionPathExists=/home/n2kowner/n2k/display.xml
ExecStartPre=/usr/bin/grep -s "mode=\"[Hh][Tt][Mm][Ll]\"" /home/n2kowner/n2k/display.xml
# Following runs WITHOUT encryption
# ExecStart=/home/n2kowner/noVNC-1.4.0/utils/novnc_proxy --vnc localhost:5901 --syslog /dev/log --listen 80
# Following runs WITH encryption
ExecStart=/home/n2kowner/noVNC-1.4.0/utils/novnc_proxy --vnc localhost:5901 --syslog /dev/log --listen 443 --cert /home/n2kowner/.ssh/self.pem
ExecStop=pkill -f "/home/n2kowner/noVNC-1.4.0/utils/novnc_proxy"
Restart=on-failure
ExecReload=/bin/kill -HUP $MAINPID
KillMode=process
Restart=on-failure
RestartPreventExitStatus=255
Type=simple
RuntimeDirectory=/home/n2kowner/noVNC-1.4.0/utils
RuntimeDirectoryMode=0755

[Install]
WantedBy=multi-user.target

Thank you - Richard

[Pierre Ossman]

On 07/11/2024 18:10, Richard Mixon wrote:
> novnc_proxy is called from service unit file
> /etc/systemd/system/noVNC.service. Here are the contents:
>
> [Unit]
> Description=Init file for noVNC 1.4.0 proxy
> Documentation=
> After=network.target auditd.service
>

Might it simply be starting before the network is fully connected? Does
the service work if you start it manually once the machine is running?

[Richard Mixon]

Pierre,

Thank you! That was it - putting a 15 second wait in the startup script seems to have fixed it.

Question: Is there a reason to prefer allowing novnc_proxy to download/install websockify versus preinstalling the package with "apt install websockify" ? 

I've tried both ways and they both seem to work. Running "apt install websockify" does install some additional packages:

The following additional packages will be installed:
libblas3 libgfortran5 liblapack3 python3-deprecated python3-jwcrypto python3-numpy python3-typing-extensions
python3-websockify python3-wrapt
Suggested packages:
gfortran python3-pytest

Thank you again.

[Richard Mixon]

Bump. Any input on using the packaged websockify versus the automatically (by noVNC) downloaded websockify?

Thank you -much - Richard

[Pierre Ossman]

On 08/11/2024 18:15, Richard Mixon wrote:
> Pierre,
>
> Thank you! That was it - putting a 15 second wait in the startup script
> seems to have fixed it.
>

> *Question:* Is there a reason to prefer allowing novnc_proxy to

> download/install websockify versus preinstalling the package with "apt
> install websockify" ?
> I've tried both ways and they both seem to work. Running "apt install
> websockify" does install some additional packages:
>

Installing via apt will likely give you a stable release, rather than
the current development version. So that is likely more preferred.

That said, websockify does not get that much attention. So there is
likely not too much difference between the two.

[Richard Mixon]

That helps. I still wonder why the "apt install websockify" needs the additional packages but the directly downloaded websockify seems to work without them. Any ideas? From before ...

Running "apt install websockify" does install some additional packages:

The following additional packages will be installed:

libblas3 libgfortran5 liblapack3 python3-deprecated python3-jwcrypto python3-numpy python3-typing-extensions

python3-websockify python3-wrapt

Suggested packages:

gfortran python3-pytest

Not a biggie, they don't take up that much space - just curious.

Thank you again.

[Pierre Ossman]

On 13/11/2024 18:29, Richard Mixon wrote:
> That helps. I still wonder why the "apt install websockify" needs the
> additional packages but the directly downloaded websockify seems to work
> without them. Any ideas? From before ...
>

They look to be the optional dependencies for websockify. If you haven't
encountered any issues, then I would say those optional features don't
seem relevant for your use case.