SSL support for web containers


SSL support for web containers

Last updated January 3rd, 2019

SSL provides a secure connection between your web containers and your visitors' web browsers.

You can easily improve the security of websites running inside your web containers by enabling SSL and thus allowing data to be transmitted securely.

More information about SSL can be found here.

How do I enable or disable SSL on a web container?

Enabling SSL on one of your web containers is as easy as clicking a button.

From the container management page for a web container, you will see a 'SSL' section near the bottom of the page:


Clicking the 'Enable SSL' button will issue a SSL certificate and automatically configure it for use.

Once enabled, you can easily disable SSL again by clicking the 'Disable SSL' button.

How does SSL work on my web container?

We have integrated our Cloud Container platform with LetsEncrypt, a free, automated and open certificate authority. This allows us to very quickly and easily request SSL certificates to be issued for your web containers with no additional cost. LetsEncrypt do enforce a rate limit on certificates though, and on certificates with the same domains/hosts they can only be renewed 5 times per week. Please keep this in mind when making changes to your containers.

More information about LetsEncrypt can be found here.

Can I use my own SSL certificate?

Yes, simply send through an email to us at and we can either supply you with a brand new SSL certificate or if you already have a certificate we'll be happy to set this up for you.

For additional information on purchasing a SSL certificate from us, please see our SSL Certificate pricing page.

How can I enforce HTTPS on my web container?

With Cloud Containers the traditional approach to redirection may not work, because all of the requests are served by a reverse proxy. Instead, we recommend leveraging the X-Forwarded-Proto header; modify your web server configuration files as follows:

For containers running Apache webserver:

RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

For example, with a default Apache based website container, the 000-default.conf file can be modified with these lines to force such redirection:

SetEnvIf X-Forwarded-Proto https HTTPS=on

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond %{HTTP:X-Forwarded-Proto} !https
    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

You can find this file in your home directory, inside the configuration folder: config/apache2/sites-available/ Alternatively, the same instructions can be instead added to your base .htaccess file in your public directory.

For containers running Nginx add the following to server directive:

if ($http_x_forwarded_proto != 'https') {
    rewrite ^ https://$host$request_uri? permanent;

For example for a Nginx container the configuration will look something like the below:

server {
    listen 80 default_server;

    # Your other config here.
    # and here...

    if ($http_x_forwarded_proto != 'https') {
        rewrite ^ https://$host$request_uri? permanent;

Important note, the containers must be rebooted for the change to take place: log into the SiteHost control panel, find the container you have modified the configuration of and press the Reboot button.

Can we improve this article? Suggest an improvement to this article.

Suggest an Improvement

Thank you for helping us to improve this Knowledge Base article. Please type your suggestions below:

Still need help? Get in touch with us.

If you aren't able to find the help you need then please send us a question and we can help you further.