Custom Domain & SSL
Custom Domain — 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.
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.
Setting Up a Custom Domain
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 steps:
1. If you haven’t already told Localist Support the domain you will be using, please send a note to email@example.com so that we can set a required configuration on our end.
2. Through your registrar, create a CNAME record to point your custom domain to your Localist placeholder URL, yourorganizationsname.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.
3. Finally, 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.
Setting Up SSL
1. In order for Localist to enable SSL for your platform, we will need to know what custom domain you will be using. However, the domain does not need to be set up through your registrar or placed in your calendar settings.
2. Localist will provide the CSR (certificate signing request)and it will need to be submitted to your certificate authority.
- Format :apache2 + mod_ssl/ .pem
3. After signing, send the certificate back to firstname.lastname@example.org and we will configure it on our end. Note: When serving your calendar over SSL, make sure that your wrapper only references secure links.