Set up SSL for your Custom Help Domain

Before starting the steps in this article, first follow the steps for setting up a custom domain described in this article.

Now that you have configured your DNS and Drift Help to use a custom domain for your documents, you will notice that your Help pages are showing on HTTP rather that HTTPS (Secure HTTP.) This is because there is no SSL certificate specific to your new custom domain available to certify that the connection between your browser and the Drift Help server is secure.We would like to have this show up as secure like this:Due to the dynamic nature of the custom domains, this must be set up on the host domain side of the connection (much like the CNAME set up with your DNS provider.) There are several ways to about this.

In order for your custom domain to use HTTPS, the connection must be configured as a proxy, not an alias.

SSL using Cloudflare

If you use Cloudflare as your DNS provider, this is the easiest way to configure SSL for your custom Drift Help domain. First, go to the 'Crypto' section and set your SSL configuration to 'Flexible' or 'Full' - not Full (strict).

Next, go to 'Page Rules' and create a new Page Rule that redirects all HTTP requests to HTTPS by entering your Drift Help custom domain followed by an asterisk in the 'If the URL matches:' form, and selection 'Always User HTTPS' in the drop down of the 'Then the settings are:' section. Hit 'Save and Deploy' and Cloudflare will automatically generate an SSL certificate attached to any requests to your custom domain.

SSL using AWS CloudFront

Setting up SSL using CloudFront is a bit more complicated, but never fear, we'll walk through it step by step!

First, sign into your AWS account and select CloudFront as the service. Select 'Create Distribution' then hit 'Get Started' under the 'Web' section.

Start filling out the form. You'll want these parameters:

  • 'Origin Domain Name' and 'Origin ID' should be your default drift.help subdomain (i.e. exampleapp.drift.help)
'Query String Forwarding and Caching' needs to be be 'Forward all, cache based on all'
 
  • 'Viewer Protocol Policy' should be 'Redirect HTTP to HTTPS'
  • 'Allowed HTTP Methods' should be 'GET, HEAD, OPTIONS'
  • 'Query String Forwarding and Caching' should be 'Forward all, cache based on all'
  • In 'Alternate Domain Names (CNAMEs)' enter your custom domain (i.e. help.exampleapp.com)
  • Select 'Custom SSL Certificate' under 'SSL Certificate' Here you can attach an existing SSL certificate you have available on Amazon Certificate Manager, or generate a new one for your custom Drift Help domain using ACM.

Hit 'Create Distribution' at the bottom of the page now. This will take you back to the main CloudFront distributions page. Click on the distribution you just created to see details, and copy the 'Domain Name' field (highlighted in the image below:Now, go to Amazon Route 53 and reconfigure your DNS to route requests to your custom domain to your CloudFront distribution instead of directly to you drift.help domain:

CloudFront takes 15-30 minutes to make a new distribution live, but afterwards your requests to your custom domain should now be automatically routed to HTTPS! Please note that if you use this method there may be somewhat more edge caching of your Drift Help content, so if you are frequently updating your documents you may see some delays in your changes being visible from browsers.

Did this help answer your question?

thumbs up
thumbs down

Thanks for the feedback! 🙏🏽


Help by drift