Table of Contents
Setting Up a Custom Domain
Every HelpDocs customer gets a custom subdomain that looks a little like this: <your subdomain>.helpdocs.io. But if you want to take the customer experience from good to great, you'll want to set up a custom domain.
Every HelpDocs customer gets a subdomain that looks like this: <your-subdomain>.helpdocs.io. Subdomains work great for most customers.
But if you want to take your customer experience from good to amazing, you'll want to set up a custom domain. Something like support.yourapp.com.
Setting up a custom domain is super simple. But if DNS and CNAMEs aren't your thing, forward this article to your developers.
Setting up your custom domain
Log into your DNS provider. This could be Route 53, GoDaddy, or whoever manages your domain. Create a new CNAME record for your chosen subdomain.
Point it to domains.helpdocs.io. Set the TTL as low as possible.
If you're using Cloudflare for DNS, your record should be grey-clouded with the proxy turned off. Orange clouding can cause issues.
domains.helpdocs.io exactly as written. Don't substitute your HelpDocs subdomain.
Now you need to tell HelpDocs about your custom domain.
- Head to Settings > General in your account
- Type your custom domain into the field
- Hit Save Changes
DNS providers aren't always as fast as we'd like 🙁
You might need to wait up to 48 hours for changes to take effect. Don't worry though. You can still access your Knowledge Base at your original subdomain during this time. Once propagation completes, visiting your custom domain should display your Knowledge Base.
Add SSL to your custom domain 🔒
All HelpDocs plans come with free SSL certificates. There's nothing extra to pay and it only takes one click. Here's how to add SSL to your custom domain:
- Make sure your custom domain works without SSL first
- Head to Settings > General
- Next to Custom Domain, click Request SSL
- Your certificate should be ready in a few secondsIf your certificate doesn't appear after several minutes, contact support and we'll help you debug 🐛
- Once SSL is working, the Request SSL button will disappear. You'll see
https://in the domain field prefix
letsencrypt.org to your CAA record.Troubleshooting common issues
Running into problems? Here are the most common issues and how to fix them:
Issue | What's happening | How to fix it |
Incorrect CNAME target | Your CNAME is pointing to the wrong domain (like your HelpDocs subdomain instead of | Update your CNAME record to point to |
SSL rate limits | You've requested too many SSL certificates in a short period | Wait 24 hours before requesting another certificate. There's a daily limit on certificate requests |
Internal error | Something went wrong on our end | Contact support and we'll investigate what's causing the issue |
Error validating domain | DNS servers are down or not responding | Wait a bit and try again. If the problem persists, check with your DNS provider to make sure their servers are operational |
Moving a domain to HelpDocs with zero downtime
You can move your existing docs to HelpDocs without any downtime. Here's how:
- Enter your custom domain in HelpDocs Settings > General and hit Save
- Update your domain's CNAME to point to
domains.helpdocs.io - Wait for your custom domain to show HelpDocs content
- Optional: Generate an SSL certificate in Settings > General by clicking Request SSL
Custom domain via CloudFront
Using Amazon CloudFront with your custom domain? By default, CloudFront doesn't forward your visitors' User-Agent to HelpDocs. It replaces it with "Amazon CloudFront" instead.
This may break some analytics functionality like:
- Pageview analytics
- Browser and device data
- Language detection
- AI crawler identification
- Bot filtering
Fix: forward viewer headers with an Origin Request Policy
- Head to your CloudFront distribution in AWS Console
- Head to Behaviors and edit the behavior pointing to HelpDocs
- Set Origin request policy to:
Managed-AllViewer (recommended): forwards everything and restores full functionality
Managed-AllViewerAndCloudFrontHeaders-2022-06: same as above plus CloudFront's geo/device headers
- Set Origin request policy to:
Using a custom policy? Make sure it forwards:
User-Agent, Referer, Accept-Language, Cookie, and Host. You can also add All Sec-* headers. They're optional but highly recommended.
- Save the changes. CloudFront will update in 1-5 minutes
What did you think of this doc?
Can I Schedule a Demo?
Understanding Smart 404 Pages