Thanks exactly what I need to know. We now have a problem where we have followed your documentation regarding setting up an ssl site (keep in mind this site is already set up and live on http) but the site is now showing on the root domain as not being secure, your connection is not private. This is because the www. CNAME record has not propagated yet and is still set to the unsecure site. So we are now stuck with a site that is indicating to people it is insecure.
Why is there no documentation on your site to warn of this scenario? I do not count the NOTE: It may take up to a few hours for DNS changes to take effect. as an applicable warning. You should state something that says if you are switching from non-secure to secure via www do not change the IP addresses on the root name until the www CNAME had propagated otherwise your site will give you security warnings.
I’m certainly not impressed with the fact that our site is not only down but looking like it’s some kind of dodgy spam site.
What do you suggest we do about this?
Ellen MacArthur Foundation
The Sail Loft, 42 Medina Road, Cowes, Isle of Wight, PO31 7BX
t: +44 (0) 1983 296463
e: firstname.lastname@example.org email@example.com
Order our http://tiny.cc/newdynamic2 latest book today, A New Dynamic 2: Effective systems in a circular economy
Charity Registration No. 1130306 • OSCR registration no. SC043120 • EU transparency register N°206816021848-17
This e-mail is confidential. It is intended for the named recipient(s) only. If you have received in error, do not copy
or disclose its contents. Please notify us immediately and delete the e-mail from your computer.