VNC configured port not what is being used.

[phebert]

VNC configured port not what is being used. For example: configured VNC Port: 15553 is only working on 14553. using the "<...>VNC" link it opens on 14553. No response on 15553. I only figured this out when trying to port-forward it on my router. This is happening on ALL of my VMs.

Found an old post, legacy; replied there but I'm not sure I will get a reply from that thread in the legacy section.

Virtual Machiene autoconfigured VNC port will not load the correct port in new browser window.

I have created a Ubuntu Virtual Machine. It lists the VNC port as 5891. When I star the VM and try to access through the ... and click on VNC it brings me to a"this site can not be reached" page. I noticed that the port is also different 5791/vnc.html?autoconnect=1. How do I fix this? Even...

www.truenas.com

Is this something I am doing wrong or is this a bug? Has it been reported?

 

[Chlorus]

I think I'm seeing the same issue - the VNC button that loads a URL with the port & vnc.html?autoconnect=1 gives me a "This site can't be reached" error

 

[scorpia1414]

Same issue