Due to several browsers dropping/disabling support for NPAPI we have introduced an experimental HTML 5 serial console into SolusVM v1.17 (currently only available to admins). To use the console, a number of dependencies will need to be installed from the v2 repositories. We hope to introduce it to the client areas once it has been tested by administrators.
Installing the Repositories
All the necessary repositories are installed on the Master server along with the installation of SolusVM Software.
Installing the Serial Console Dependencies
To install the console the following will need to be done in SSH (as root) on the master server:
- To enable the serial console, navigate to Configuration > Settings > Virtualization and set Html 5 Serial Console Admins & Html 5 Serial Console Clients to On then click Update.
- Check the hostname for the master is set correctly and make sure the DNS resolves. Nodes > Edit Master Node > Hostname. Even if the hostname is correct we advise you re-update it.
The serial console uses SSL between the browser and the master server so a valid certificate is recommended. In most cases you will already have a valid certificate for your master which lighttpd will be using. You can use this certificate with the websocket by copying the existing certificate to the following locations:
/usr/local/svmstack/nginx/ssl/ssl.crt should contain the certificate.
/usr/local/svmstack/nginx/ssl/ssl.key should contain the private key.
It is advised you use the default locations specified above when copying the certificates. This is an experimental feature so the configuration files may change on updates. Keeping the default locations will ensure the service continues to run and extra modules can automatically use the certificates without further intervention.
Now restart the service:
To use the serial console navigate as an admin or client to a virtual servers manage page (Xen PV & OpenVZ only). Click the Console icon and create a session. After the session has been created you can click on the HTML 5 Console button to open it. If all goes well a new window should open and the console should show.
The websocket comes with a handy logging feature. The log is located at /usr/local/svmstack/sshwebsocket/log/debug.log on the master server. Logging is enabled by default.
If you are having issues connecting or you get no output in the console window - check the following:
- You have set the master hostname correctly. Update it again to make sure it is correct.
- You have installed the valid SSL certificate. Sockets won't work correctly without it and many browsers won't allow you to use a self signed certificate.