Steps

Once your Website is published and configured with a custom domain, you can navigate to the "Site Settings" section, and click on "Site SSL". This will take you to the page where you can set up SSL.

Once there, simply click "Generate certificate" to create an SSL certificate.

The process, which includes provisioning the request to Let’s Encrypt and configuring the newly generated SSL certificate, is fully automated and may take up to 30 minutes. During the provisioning process, an “In progress” status indicates that the request is being handled.

Once completed, the provisioning status is changed to “Complete”, and an approval email is sent to the account owner.

You can enable the Force SSL option to make sure that your Site will always be accessed via SSL. Any visitor will be redirected to the secure connection once this switch is turned on. 

An SSL certificate is never deleted by the Responsive Site builder unless the user clicks on the “Remove certificate” link. 

Recreating your SSL Certificate

If you have previously set up your domain using the method involving using a CNAME and 301 Redirect and have changed your DNS settings to reflect a CNAME and two A Records, you will need to recreate your SSL Certificate.

1. Navigate to your editor > Settings > Site SSL.
2. Click on "Recreate Certificate".
   
   
3. You will need to wait for the certificate to be recreated.
   
   

Important details about secure connections

• You will need to recreate your SSL certificate if you switched your DNS settings from using the CNAME and 301 Redirect method to the CNAME and two A Record method.
• Certificates for Sites are valid for three months. Two weeks prior to the end of the certificate, the Responsive Site will renew the certificate to ensure that the Site remains secure and valid.
• Once your Site has been set up with a certificate you will see a small lock icon in your Dashboard to indicate that the Site is a secure Site. 
• Duda uses HSTS Policy (HTTP Strict Transport Security). This feature helps protect against protocol downgrade attacks and cookie hi-jacking. 
• The Responsive Site's secure connection uses the DV (Domain Validated) certificate.
• Our SSL implementation is not compatible with any version of Internet Explorer on Windows XP (but will work on Chrome or Firefox).
• Not compatible with Android 2.3 and earlier.
• We've added logic to the platform that makes sure we don't redirect traffic to HTTPS for these devices. If a user on an incompatible browser attempts to load the HTTPS version of the Site, a security error/warning will appear. However, if the user visits the HTTP version of the Site, the responsive Site will simply not load the HTTPS version.
• Currently, our SSL solution does not support internationalized domain names (names with non-Latin characters, i.e www.bücher.de)

Using custom or third-party code in SSL sites

Due to HTML standards, HTTP or non-secured content cannot be displayed in HTTPS or secure Sites. This means that any custom code which relies on loading content from an HTTP server will not work in an SSL Site. If you need to use code which normally loads from an HTTP server, we recommend either:

• Requesting HTTPS-friendly code from your code provider
• Disabling HTTPS for your Responsive Site

As our Responsive Editor displays by default on an HTTPS connection, one good way to test whether or not code will work in the final Site is to see if it works in the editor. If it does not, it is equally unlikely to work in a live HTTPS Site.