In this tutorial I will show you, how to fix Server disconnected(code:1006) while accessing NoVNC error in SolusVM.
Issue (Problem or Question) -the situation in your words-what are you trying to do or what is not working.
NoVNC is not working working.
Getting an error “Server disconnected(code:1006)” while accessing NoVNC.
Environment – What Product (s) (hardware,software,network,
Has anything been changed recently? such us upgrades,deletion. The environment description should be as precise as possible, with standard ways to document product names and versions.
Valid SSL for the master’s server hostname.
SolusVM needs 1.15.03 and above.
Error will arise in both admin and client panel.
It works in KVM and XEN HVM virtualization.
Resolution – the steps required to resolve problem
To check the settings for the NoVNC in solusvm.
i) Enable noVNC in the admin area.
ii)Enable noVNC in the client area
iii)Specify the port number the websockify daemon runs on.
iv)Specify the location you want the websockify daemon to run. Whether master or slave server.
To check the file /usr/local/solusvm/data/
config.ini in Master server.
i)In this file we have to check the ports and the below lines.
- use_remote_hostname = true —-> If it is true means hostname should be in hostname fileld in edit node.
- socket_dest_public = false—.> If it is true means IP should be in hostname fileld in edit node.
To check the cert.pem file in the location /usr/loacal/solusvm/includes/
i)We could find out the CERT file in the lighttpd configuration.
- The mostly file name in solusvm.pem we have copy to the location /usr/loacal/solusvm/includes/
novnc and rename as cert.pem
- The cert.pem file should located as /usr/loacal/solusvm/includes/
Refer the below document: