Skip to Content
Help Centre and FAQs

HTTPS and SSL certificates

Enable HTTPS with a free Let's Encrypt certificate and check that it covers every hostname you use.

How do I enable HTTPS on my website?

Before requesting the certificate, check that the domain and any aliases you want to include point to your hosting server.

  1. Under Websites, edit the site and find the SSL certificate section.
  2. Choose a new free Let's Encrypt certificate, review the hostnames it will cover and request issuance.
  3. Check the control panel notifications to confirm that the certificate has been issued.

Once the certificate is active, open the domain over HTTPS and check that your browser displays the site without a security warning.

List of websites with a tick in the SSL column for the example domain.
A tick in the SSL column means SSL is enabled for the site. Open the domain in your browser to check the certificate.

How do I redirect visitors from HTTP to HTTPS?

Once your certificate is working, edit the website and enable the option to redirect HTTP requests to HTTPS.

Enter the address starting with http:// and check that your browser redirects you to the same page over https://.

What should I do if my certificate is not issued?

Every hostname included in the certificate must pass validation.

  1. Check that the domain and its aliases resolve to your hosting server. If the domain uses IPv6, check the AAAA record too.
  2. If you use HTTP validation, check that the site is publicly accessible and that password protection does not block validation.
  3. Check the notifications or the certificate issuance log. If you chose DNS validation, add the TXT record shown in the control panel to the DNS zone that serves the domain.

Why does my browser still show a warning after I enable HTTPS?

Check whether the warning appears only on the www address or only on one page. If the hostname does not match, check that the certificate covers it and that it points to your hosting server. If the page loads but the browser reports mixed content, check whether any images, scripts or stylesheets still load over HTTP.

After making corrections, try the affected URLs again in a private browser window.