The new software stack for SolusVM is compatible with v1.x and will allow you to use a maintained NGINX version instead of the standard lighttpd version shipped with v1.x
This documentation is for Master (UI) servers and Slave servers
The following port changes have been made to UI (master) servers:
If /etc/yum.repos.d/solusvm.repo already exists it means it's already installed and you can skip this step
yum install solusvm-release
You will need to shutdown the current lighttpd service:
service lighttpd stop chkconfig lighttpd off
Next install NGINX and the legacy configs:
Master (UI) Server
yum install svmstack-nginx svmstack-nginx-legacy-master-config
yum install svmstack-nginx svmstack-nginx-legacy-slave-config
Start the new service:
service svmstack-nginx restart service svmstack-fpm restart
You can use the excellent acme.sh script as detailed here https://github.com/Neilpang/acme.sh/wiki/Deploy-ssl-to-SolusVM
In most cases you will already have a valid certificate for your master which lighttpd would have been using. You can use this certificate with the new stack 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:
service svmstack-nginx restart
A slave can usually function on a self-signed certificate. If you require a valid certificate you can use the same process as the master certificate setup.
|There is no longer a need to add additional ports. Port 443 is now standard in the new stack and the non SSL ports have been disabled, however port 5656 is still required.|