VNC

From ISPWiki
Jump to: navigation, search
Hierarchy: VMmanager KVM ->OTHER
VMmanager Cloud ->OTHER

VMmanager uses HTML5 VNC client noVNC. websockify is used for supporting websocket.

SSL

SSL is disabled for noVNC by default, because in some browsers the client won't start, if you use a self-signed certificate.

However, if you have an SSL certificate issued for your domain, you can activate the SSL yourself. Copy the certificate into /usr/local/mgr5/etc/manager.crt, and its key into /usr/local/mgr5/etc/manager.key. Add the following option into the configuration file:

Option VncSSL

Attention! If in ihttpd.conf paths to the certificate file and key are overridden, you will still need to copy the certificate data into /usr/local/mgr5/etc/manager.crt, and its key into /usr/local/mgr5/etc/manager.key, because those files are used when connecting via VNC.

Restart VMmanager:

/usr/local/mgr5/sbin/mgrctl -m vmmgr exit

VNC network interface is defined automatically by default. The bridged networking, to which VM's network interface is connected, is used.

Starting from version 5.64 you can specify a network for VNC-server. If you want to restrict access to VNC by standard means of VNC client,use a NAT private network.

You can configure VNC network in the "Cluster settings/Policy" module.

RealVNC Viewer

In order to connect QEMU VNC using RealVNC Viewer you first need to configure the client:

VNC Viewer --> Options --> Expert --> set ColorLevel to rgb332

See also RealVNC Knowledge base