noVNC library update and error

lkthomas · August 27, 2022, 1:42pm

on an installed Foreman host, “/usr/share/foreman/extras/noVNC” code is outdated, after pulling noVNC code from the official source and update it, then go on the web UI: Infrastructure → Compute Resources → (My VM host) → “Virtual Machines” → (My VM and confirmed using VNC instead of SPICE) → Console, I see “Loading…” and nothing happen, Firefox inspect didn’t show any error, anyone know how to fix this?

lkthomas · August 27, 2022, 2:39pm

I fixed it,

github.com/theforeman/foreman

Fixes #35418 - Update websockify to make noVNC functional

theforeman:develop ← lkthomas:update_noVNC_library

opened 02:26PM - 27 Aug 22 UTC

lkthomas

+2534 -1031

Go to the web UI: Infrastructure → Compute Resources → (My VM host) → “Virtual M…achines” → (My VM and confirmed using VNC instead of SPICE) → Console, I see this error: "The connection was closed by the browser. please verify that the certificate authority is valid", I checked all my certificate setting and from shell confirmed the websockify actually fired properly, it just the web UI didn't function correctly. Somehow to noVNC library on theforeman repo is 2 years old, after updating the code from noVNC/websockify and adjust the libvirt VM to listen all interface, finally web console start working.

ekohl · August 29, 2022, 6:37pm

As I already mentioned in the PR, from a packaging perspective vendoring is highly undesirable. Instead I moved forward with Refactor #29539: Unbundle websockify - Foreman. By using a system package, it can be updated independently.

Out of curiosity, what OS is your Foreman host running? I just checked today (to verify my new PR) and on CentOS Stream 8 it was still working.

lkthomas · August 29, 2022, 7:31pm

Thanks for working on this, I am running Ubuntu server 20.04.4 LTS