As the number of hackers, identity thieves and phishing attacks is constantly increasing, it’s very important to keep the information path between you and your customers’ computers safe and private. With Enscale you can make sure you’ve got this covered by enabling the SSL feature. You can choose between the Shared (free) Enscale SSL or a private SSL certificate.
Although the Shared SSL is a quick and free solution it’s designed only for testing purposes. For all other cases (e.g. production websites, public demos, anything business critical) we strongly recommend using a Custom SSL to ensure your users see your own domain in the URL without Layershift branding, a shared SSL certificate might raise suspicions. If you try forcing your domain name in the secure connection you will end up getting browser warnings, which will only affect your credibility even more.
As its name suggests, this shared SSL is a free certificate provided by Enscale, available for use to all platform users. The certificate is issued for *.j.layershift.co.uk and it covers all subdomains under this main domain name. What this means is that you won’t be able to use SSL with a custom domain name, you’ll instead need to use this format:
https://your-environment-name.j.layershift.co.uk.
Enscale Shared SSL is intended to be used for start-up projects, staging / development websites or in any other scenarios where the secure connections are not intended to be seen by the public.
Change environment topology
icon (or on the New Environment button if you don’t already have one).
Built-In SSL
option and click Apply
: Please note that if you switch IPv4 ON for any node in your environment, the Enscale shared SSL will be automatically disabled.
Enscale's Custom SSL feature is designed for all production websites where you can install a certificate issued specifically for your domain name. To be able to install your own custom SSL certificate you will need to add a public IP to your application server or Nginx load-balancer.
This category of SSL certificates is very popular as it allows you to secure your own branded URL. There are multiple certificate types, depending on the validation process, the number of domains they cover or the level of assurance. We have a blog article explaining each certificate type in detail so please take a look.
Before you can set up a private SSL you need to make sure you have:
A public IP can be switched on from the environment Topology settings > click the on/off button to turn on then Apply.
We’re offering a large range of top-level domains so if you haven’t picked your favourite yet, you can do it easily.
After the IP address is added to your environment you need to point your domain name to the public IP.
We completely take care of the installation process for you for any certificates purchased from Layershift for use on our hosting services. However, if you’ve already purchased the certificate from a third party, here’s how you can add it to your environment:
Your website or application is now secured!