noVNC console allows to access the VPS via SolusVM UI.

As part of our Server Management Services, we assist our customers with several SolusVM queries.

Today, let us discuss noVNC in SolusVM.

noVNC in SolusVM

We can access noVNC at SolusVM > Virtual Servers > List Virtual Servers > VNC. It is available for KVM and XEN HVM VPSes.

Moving ahead, let us see how to configure noVNC.

We can set up noVNC via SolusVM > Configuration > Settings > Other

• noVNC Admin is to Disable/Enable noVNC in the admin area
• noVNC Client is to do the above in the client area
• noVNCSocket Port is the port number the websockify daemon runs on. Default is 7706
• noVNC Socket Location – Set up Master as socket Host.

We have to connect to the master server via SSH and install the necessary packages:

yum install python numpy python-ssl

Then we setup SSL certificate for noVNC and place it in, /usr/local/solusvm/includes/nvnc/cert.pem/

After that, we execute the following commands:

cat /usr/local/svmstack/nginx/ssl/ssl.crt /usr/local/svmstack/nginx/ssl/ssl.key > /usr/local/solusvm/includes/nvnc/cert.pem

systemctl restart svmstack-nginx.service

However, starting with version 1.24.09 when the VNC-console certificate expires, this action performs automatically.

On CentOS 8/RHEL 8/Scientific Linux 8 if noVNC Socket Location is set to Host Node. It does not require this action with respect to SSL-certificate for VNC.

In this case, SolusVM uses Nginx SSL-certificate files directly

We can also find several advanced settings in the masters, /usr/local/solusvm/data/config.ini file:

[NOVNC]
;;Set this to true for noVNC to access the WebSocket with the remote server's hostname. All the hostnames must resolve correctly. Default (false) is to use the IP address of the remote server
use_remote_hostname = true

;;Set this to true for the socket on the host to forward packets across the public network
socket_dest_public = false

To debug socket connections we manually start websockify on the host. Make sure to do this on the correct server and specify the correct port.

sh /scripts/websocket-stop
php /usr/local/solusvm/includes/wsocket.php --port=7706 --debug=1

After that open the noVNC console and check the logs in the terminal.

Disable noVNC console for a VPS of a client

It is also possible to disable the noVNC console for each VPS of a client. Let us see how to do that.

1. Initially, we login into the SolusVM admin area.
2. Then we disable VNC in Virtual Servers > VPS > Settings > General > VNC.
3. Finally, we reboot VPS via Virtual Servers > VPS > Reboot to apply changes.

[Stuck with the configuration? Feel free to contact us]

Conclusion

In short, we saw how our Support Techs go about noVNC.