Follow

Whitelabel URL Setup

To set up a whitelabel URL, you'll need the following:

  • The domain (that you own/control)
  • A CSR
  • And SSL Certificate

The following instructions require some level of IT knowledge as well as access to the domain control panel.


Creating a CSR

To create a CSR, you will need to create both the key and the CSR. On a Unix machine or in Mac OSX's Terminal, use the following commands:

  1. Create a key
    openssl genrsa -out <domain_name>.key 2048
  2. Create a csr
    openssl req -new -sha256 -key <domain_name>.key -out <domain_name>.csr

To get an SSL certificate:

There are lots of providers of certs (RapidSSL, GeoCert, etc.) and they provide tutorials how to do it (for example here is GoDaddy's instructions https://support.godaddy.com/help/article/5269/generating-a-certificate-signing-request-csr-apache-2-x). Recently we have been using www.ssls.com. They have relatively inexpensive PositiveSSL certificate provided by Comodo for $9/year. See https://www.ssls.com/ssl-certificates/comodo-positivessl. When buying a certificate, the provider will need to verify that you are who you say you are. This is usually done by sending an email to the email address setup in DNS (so you will need to have the domain set up in advance).


 Update DNS:

There are two ways that you can set up the DNS records so that they direct to the zerista.com site. If you are mapping the root (example.com), please use an A record. If you are using a subdomain (app.example.com), please use a CNAME. This set up should be done through your DNS provider -- generally the same as where you registered the domain, but could be separate. Here is the information for both types of setups:

To set the root (http://www.example.com):

Type: A
Host: @
Value: 38.97.204.35, 38.97.204.37
TTL: 3600

To set a subdomain (http://app.example.com):

Type: CNAME
Host: app (or everything before the first dot in your desired URL)
Value: example.zerista.com (this should be the zerista URL for your conference)
TTL: 3600

It can take up to 48 hours for DNS updates to go live. 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk