Custom Domain & SSL
Localist’s custom domain feature is an essential component in your overall white-labeling of the product as it changes the display of your Localist URL to a subdomain of your current website. Your calendar’s custom domain is set up by using a CNAME record.
Your custom domain will need to be a subdomain to your website, such as events.yourwebsite.com, and not set as a subdirectory, such as yourwebsite.com/events.
- If you do not currently own a website domain, you will need to purchase a domain from a registrar like Namecheap, pairNIC, Register, or iWantMyName. (This usually costs about $10-$40 per year.)
Once secured, follow these two steps:
Create a CNAME record to point your custom domain to your Localist placeholder URL, yourorgname.enterprise.localist.com.
This is not a forward or a redirect, but an alias. If you are setting up a redirect for the non-www custom domain, the redirect should be unmasked.
Once set, navigate to Settings > Global options and add the new domain to the Custom Domain field
It can take 24-72 hours for domain settings to propagate across the world. Confirm the domain has fully propagated before taking this step. You can confirm it through websites like https://dnschecker.org/.
Setting Up SSL
SSL (Secure Sockets Layer)is a standard security technology for creating an encrypted link between a server and a client. Serving over SSL, allows sensitive data, such as login credentials, to be transmitted securely. By default, information is sent in plain text.
When serving your calendar over SSL, your wrapper must reference only secure links.
Request a Certificate Signing Request (CSR) from Localist
Your Custom Domain will need to be chosen before this step.
Submit the CSR to your certificate authority
The certificate will need to be in the format apache2 + mod_ssl/ .pem
Return the certificate to Localist for configuration