VNC over websocket without noVNC

Hello,

Some of my users are asking me if it’s possible to run a standard VNC client over the websocket.

The context is the following:

  • nebula hosts are not on a reachable network
  • users have problems with the noVNC client (typing a backslash for example or slow console in the browser)

I would like to create a little helper to open a VNC console with a standard client, the use case is the following:

  1. Start the helper
  2. The helper connect to opennebula using ${HOME}/.one/one_auth or ask for login and password
  3. The helper list all the VMs of the user
  4. The user click an open console icon
  5. The helper get the connection informations (token and websocket informations)
  6. The helper open the websocket and expose it locally 127.0.0.1:$(random but not used)
  7. The helper start the VNC client on the listening port opened at 6.

Ideally, multiple VNC consoles could be opened in parallel.

Any idea how if this is achievable?

Regards.

Daniel Dehennin forum@opennebula.org writes:

Hello,

Some of my users are asking me if it’s possible to run a standard VNC
client over the websocket.

I finally start a little script[1], it’s far from being complete but I
can use ssvncviewer and forget the noVNC limitations.

Regards.

Footnotes:
[1] https://github.com/baby-gnu/one-sunstone-rest-client
signature.asc (342 Bytes)

1 Like