DO Ideas 2

Allow users access directly to VNC nodes instead of noVNC

Current system has several drawbacks :

- vnc enable sometimes hangs for hours and users are unable to do anything
- noVNC doesn't have a full-screen option, developer doesn't have time to implement scaling
- requires browser

I suggest you allow users to connect directly to the VNC nodes using any VNC client.
I understand security concerns, you can have the "VNC" enable function open a random port, and keep it open for new connections only 30 seconds for example.

  • Anonymous
  • Sep 11 2018
  • Attach files
  • Es Cendol commented
    September 11, 2018 18:44

    +1000 for this feature.

    My previous VPS uses SolusVM panel which provide separate VNC connection details for using with VNC client (and I am pretty sure that many others panel also provide separate VNC for direct access to the VNC node)

    In some condition, user may be prefer using VNC client rather than using web-based VNC console.

    And there are plenty issues with browser, sometime it is hanging, the VNC not displayed, browser crashed, and etc...

  • Anonymous commented
    September 11, 2018 18:44

    If there's a way to do it, I'm all in favor of the ssh console. I am visually impaired, and use a screen reader to access my computer, and also my VPS's. Unfortunately, because vnc doesn't allow sound to be transmitted over the connection to my computer, I am unable to connect using any vnc viewer or browser-based vnc system, even if the kernel-based screen reader known as Speakup is enabled on the server. A text-based console that uses standard ssh to transmit non-graphical information securely, preferably based on the authorization of my ssh key, will give unprecedented screen reader access to all aspects of a droplet, including some things I am unable to read on my own computer, i.e. GRUB and non-speaking installers that don't yet have sshd running.

  • James Cloos commented
    September 11, 2018 18:44

    ssh access to a shell console is still better than vnc.

    Settings could permit associating one of one’s uploaded ssh keys with said console access, to avoid passwds.

    And even for vnc, ssh keys would be best.

  • Joel Martin commented
    September 11, 2018 18:44

    noVNC definitely works well in Firefox and Opera and should also work in IE9 or later.

    Also, scaling support is being worked on by another developer. It's not a big task but you're right that I don't have time to work on it myself. Full screen should be pretty simple to implement once general scaling support is properly implemented implemented.

  • Moisey Uretsky commented
    September 11, 2018 18:44

    We are looking into this and especially as it relates to giving access to grub.

  • Anonymous commented
    September 11, 2018 18:44

    another drawback: noVNC only works with chrome browser, not firefox, ie, opera, etc