noVNC console is killing direct VNC access port

[RCK]

Hello,

I'm running Qemu with the following VNC args

args: -vnc 0.0.0.0:101,password

Then I'm setting the password with

pvesh create /nodes/localhost/qemu/101/monitor -command 'set_password vnc mypasswd'

This let me connect regular VNC client to VM on the 6001 port, and it works very well

My problem is since proxmox 3.3, the great noVNC console is shutting down the VNC port when launched.
When I start a noVNC console, the 6001 port no more reply (which could be fine during the noVNC session).
The problem is when I close the noVNC popup, proxmox doesn't give me back the direct VNC port.

Any idea how to restore the vnc server on port 6001 when noVNC is closed ?

Thanks !
RCK

 

[RCK]

The problem is the same with Java applet VNC console.
Log show me that the "vncproxy" task is ended, but I does not give back the local VNC port

Sep 30 10:42:12 pdm999 pvedaemon[463391]: <root@pam> starting task UPID:pdm999:00073CD7:07354CFF:542A6CE4:vncproxy:197:root@pam:Sep 30 10:42:12 pdm999 pvedaemon[474327]: starting vnc proxy UPID:pdm999:00073CD7:07354CFF:542A6CE4:vncproxy:197:root@pam:
Sep 30 10:42:17 pdm999 pvedaemon[463391]: <root@pam> end task UPID:pdm999:00073CD7:07354CFF:542A6CE4:vncproxy:197:root@pam: OK

 

[jdrews]

Any updates on this? I just ran into this issue as well, after upgrading to 3.3.

 

[RCK]

I still have the same problem.
When vncproxy is launched from Web interface, it hack the qemu vnc local port and never give it back, even when the vncproxy task ending.