Last Edited: Apr 23, 2019
There are four steps to putting a site live with Siteglide. We’ve outlined each of these below with examples.
We are working to provide more automated methods of putting a site live so partners will be able to click a button in their portal to submit payment and be provided with the relevant information and controls to set up domain and SSL certificates.
Get in touch with us via the intercom chat icon in your Admin and let us know which site you’d like to put live and which plan you’d like for it. If you’re unsure ask us to take a look at your site and we can advise you.
We’ll send over a Stripe payment link, that you can use to enter your details and confirm recouping payment, right there in the chat.
Stripe forces HTTPS for all services using TLS (SSL) and only serve via verified TLS connections. All card numbers are encrypted at rest with AES-256.
Once payment has been confirmed we will be able to edit your site’s domain settings and initiate the go live process.
Option 1: Nameserver change (AWS Route 53)
1. Notify Siteglide who will set up a Hosted Zone and provide the 4 Nameserver values to set up in the Domain DNS control panel
2. IMPORTANT: Ensure you notify Siteglide of ANY other records that need to be set up including but not limited to MX records, CNAMEs, A Records, TXT records or SRV records. They will NOT transfer automatically and will be lost.
Example of NS record values:
Option 2: CNAME and A Record pointed to the AWS Loadbalancer (IP address is NOT possible)
1. Notify Siteglide who will add the domain and provide the Loadbalancer details.
2. Create a CNAME for the www record and point it to the load balancer (this is a domain and cannot be an IP address). Also create an A Record for the root/@ that points to www. If you cannot create the A record to www then point it to the IP address of your provider/domain. Alternatively use a redirect/forwarding. See known issues section below.
Example of CNAME record values:
You will need to remove any existing CNAME Records and A records that point to your previous site.
Please note that it is not possible to write A Records that point to an IP address, it has to be to the loadbalancer domain. If the domain DNS control panel does not support this and cannot redirect to the CNAME then the Nameserver route might be the only option or moving to Google DNS (or another reputable DNS provider that supports FQDN for A Records).
1. Check that there are no links on the site that are manually defined with
http:// they should all be using
https:// to maintain the integrity of the SSL certificate.
2. Siteglide will also turn on your free SSL certificate (if required) which will require DNS authentication. To do this, you will need to add a CNAME record to the DNS configuration for your domain (see known issues section below for GoDaddy among others). It will look similar to this one:
Once the relevant CNAME and A records have been set up and the SSL verification approved it’s a case of waiting for the domain to propagate across the internet. This can take up to 72 hours, but is normally within 12 hours.
This registrar does not allow FQDN for A records, only IP addresses so the workaround is to route the @/root to the www CNAME and it then direct onto AWS Route 53. You can contact Nework Solutions or view their docs for specific support.
You cannot create an A record to anything but an IP address so trying to do @ to www will not work. Instead do @ to the GoDaddy Server or forwarding IP address or use domain forwarding (Screenshot).
GoDaddy also do not allow a full stop/period at the end of a domain meaning you cannot setup the CNAME DNS verification for SSL.
Instead you will need to use Email Verification which will send an email to the following addresses:
firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org).
The client will need to approve before this can go live by clicking the link and button on the subsequent page. Please let them know to look out for emails from Amazon Web Services and to follow the steps.