Securing secondary hostnames for SolusVM Masters


We have internal names that we give to Solus Masters that customers have access to. In some cases the customer may want to have their own hostname setup for their own customers which they would want to have secured using the internal letsencrypt function that Solus provides. In order to do this I modified the file:

/usr/local/svmstack/letsencrypt/letsencrypt/config.json

From the following code for the main hostname:

{"domain":"server.bbrader.com","www":false}

to

{"domain":"server.bbrader.com","www":false,"domain":"customers.hostname.com","www":false}

After this I ran the /usr/local/svmstack/letsencrypt/letsencrypt script once more and this correctly obtained and installed an ssl on the customers requested hostname.

Leave a Reply

Your email address will not be published. Required fields are marked *

*