Open johrstrom opened 4 years ago
Native VNC clients should be used if they're accessible. This means that we should probably update the native tabs to provide a link with the correct URL. We provide osc://
for our osc VNC viewer, but I wonder if say Windows/Mac will open tigerVNC when vnc://
URLs are clicked.
If they have the network connectivity to a compute node.
The OSC VNC client was a bit before my time, but we may have to dig into how it worked because we do not now have connectivity to compute nodes so I don't believe it would even work now unless we proxy the tcp connection through apache...
a quick read of the osc-connect docs indicates it uses an ssh tunnel so I suppose the current panels are actually as correct as they can be.
Apparently VNC clients like TigerVNC or REAL VNC are also inaccessible. Another option to investigate is X11 forwarding.
reviewed, alternatives need further investigation
noVNC is basically completely inaccessible because it's a
<canvas>
element with no text alternative.It would be a huge undertaking to fix it or port to a different solution. So this ticket is likely just going to be a discussion forum for the team & community to chime in on what alternatives we could take (if any).
┆Issue is synchronized with this Asana task by Unito