White Label SSL Update FAQ

You may have recently received an email from us advising that your site needs to be moved to our secure SSL server.

 

This SSL update is important because:

 

  • Your users including clients may see a message advising that your site is unsafe.
  • Knowing your site is secure builds trust for your users (and helps with GDPR compliance).
  • Social sites are likely to block connections coming from http sites in the future and this would affect the ability to setup services for that site and to post to or retrieve information for existing services.
  • Some features will start requiring a https connection. Currently, this only applies to the Chrome extension / bookmarklet as this is needed for this feature to work on https sites.

 

FAQs:

What does SSL mean?

SSL provides a secure channel between two machines or devices operating over the internet or an internal network. One common example is when SSL is used to secure communication between a web browser and a web server. This turns a website's address from HTTP to HTTPS, the ‘S’ standing for ‘secure’.

 

Is there a cost? 

No, we will not be applying any fees or charges to cover the change.

 

What’s needed on my end?

The CNAMEs for your White Label will need to be updated. You will have two CNAMEs setup for your White Label pointing to our servers. 

You should have two CNAMEs URLs set up which will look similar to the below:

http://api.whitelabelname.com

http://social.whitelabelname.com

We will have looked to include the specific URLs for your White Label CNAMEs in the email sent to you.

To update these CNAMEs, please:

  1. Login to your Domain’s registrar
  2. Now, access the DNS Manager / DNS Settings / DNS Dashboard / Control Panel or C Panel (the interface will be different depending on the registrar)
  3. Locate the CNAMEs that you have created when setting up your White Label
  4. Change the URL pointing to d2l5ppwntr6d2n.cloudfront.net to point to app.socialcloudfront.com
  5. Change the URL pointing to whitelabel.sendible.com to point to api.socialcloudfront.com
  6. Please Save the changes

Once you've done this, you can check that the CNAMEs are pointing to the endpoints correctly by going to this site: https://www.misk.com/tools/#dns/

Then, enter the first CNAME URL, check that it's pointing correctly and then enter the second CNAME and check this.

Please Note: Until your CNAME changes have consolidated (this can take an hour or more depending on your provider) the changes will not be reflected when checking using the site listed above.

 

When should I do this?

There will be a slight downtime once you update the URLs. This means you will not be able to log into your White Label for a period of time (this can vary by hosting provider) but don’t worry, everything set up on your White Label will still work, eg. posts will still be sent out, reporting data collected, etc. Because of this, we highly recommend that you update the URLs outside of your normal working hours.

 

Will posts still be sent out during the downtime?

Yes, as this is handled by our backend, this does not rely on the White Label being accessible and posts will still be sent out as normal during this time.

Have more questions? Submit a request