vnc password

[pvenub]

[h=2][/h]

am using the first part of the following wiki to create a vnc connection:

https://pve.proxmox.com/wiki/Vnc_2.0

issue I am having is the instruction:

6. If you have enabled the VNC password encryption you need to do the step a listed just below as well:

a. go into the console within the web panel and run set_password vnc YOURPASSWORD
NOTE: the console command has to be run every time you start up the VM because it doesnt remember the password for some reason?

7. connect via the ip address and port, away you go!

when I try to use the set_password vnc ****** on the server I receive bash: set_password: command not found

So I have a good vnc connection though I cannot seem to instantiate the password? I am sure I am missing something simple here?


​

 

[Mr.Holmes]

Hello!
"set_password vnc YOURPASSWORD" has to be put via web-interface https://PROXMOX_SERVER:8006, "Monitor" tab (and NOT via ssh-console!), i.e.: Datacenter -> NODE-name -> VM-id -> Monitor
Verified using TightVncViewer and TigerVNC
Regards Mr. Holmes

 

[pvenub]

Thank you so much. I will test the procedure in a few minutes. Things are so simple after having them pointed out

One more question, what is the 'monitor'?

 

[Mr.Holmes]

Hello pvenub,

"Monitor" is an utility for controlling running kvm machines providing a kind of "expert-mode".

It is implemented by the pm command (/usr/sbin/qm on the server). What you see in the "Monitor"-tab is what you get after enter into interactive
mode by typing "qm monitor VM-id" in the linux console.

Best regards

Mr.Holmes

 

[pvenub]

Thank you very much for explaining that process! I will try to go into the wiki and amend the post to clarify how that
is done from the 'monitor' in the web gui.

One more quick question: Is there a way to restart whatever service the vnc depends on so if I make VNC related changes to the .conf
file that they will take effect without me having to reboot the server, which I have had to do up to this point?

Thanks again,

 

[Mr.Holmes]

You have to shutdown and start (reboot is not sufficient) the virtual machine, but not the PROXMOX server.