DO Ideas 2

Use a commonly unblocked port for the Console VNC access

I know this is not an easy thing to just suggest, but it would be handy if the VNC Console used a port such as 443, for when people are on a library network, uni network, etc, and whatever port the VNC currently uses is blocked :)

  • Tom
  • Sep 11 2018
  • Will not implement
  • Sep 11, 2018

    Admin Response

    The console service is provided by the hypervisor and not the droplet itself. As there are multiple droplets on each hypervisor node, each requires it's own port to provide the service. Currently this means that multiple ports are used so it is unfortunately not as simple as just setting a commonly unblocked port.
  • Attach files
  • ryan commented
    September 11, 2018 16:48

    Thanks for the suggestion. The console service is provided by the hypervisor and not your droplet itself. As there are multiple droplets on each hypervisor node, each requires it's own port to provide the service. Currently this means that multiple ports are used so it is unfortunately not as simple as just setting a commonly unblocked port.

  • Tom commented
    September 11, 2018 16:48

    edit: This happened to me today at the library, couldn't SSH in, so I tried going to the VNC console to change the SSH port to 443, but I couldn't get in! I know this isn't your fault at all, it's the fault of the library's sysadmin.