Wildcard SSL issues

Hello. We have a wildcard SSL for main domain wbu.com. We have a subdomain and a different website located at https://www.franchise.wbu.com. We recently launched a new wordpress site and pointed the franchise subdomain to a new directory hosted at Rackspace. After that change, the franchise subdomain is no longer secure. I called Rackspace and they said I need to contact Cloudflare for support. Both wbu and franchise both have A records and are pointing to a specified IP. Thanks!

Hi @barrettc,

I expect that the issue here is that the subdomain is too deep. The Cloudflare wildcard cert would cover franchise.wbu.com but not www.franchise.wbu.com.

The Cloudflare universal certificates cover example.com and *.example.com.
This means that they cover any subdomain one level above the domain you signed up with. It will cover www.example.com and subdomain.example.com, as these are one level above the root domain, example.com. The certificate will not cover www.subdomain.example.com or a.b.example.com, however, as these subdomains are too deep.

You can read more about this and the solutions in this community tutorial.

You also seem to have some mixed content issues on franchise.wbu.com.

Mixed content errors mean that your website is being loaded over HTTPS but some of the resources are being loaded over HTTP. To fix this you will need to edit your source code and change all resources to load over a relative path, or directly over HTTPS.

For example, if you load your images with a full URL:

<img src="http://example.com/image.jpg" />

You would want to change this to:

<img src="//example.com/image.jpg" />

By removing the http:, the browser will use whichever protocol the visitor is already using. An alternative option would be to enable the Automatic HTTPS Rewrites feature that can potentially fix these errors for you automatically. Do be aware that resources loaded by JavaScript or CSS will not be automatically rewritten and mixed content warnings will still appear.

See this Community Tip for further details

The strange thing is we developed the site using the directory where the site currently sits on the server and the subdomain was working fine for both franchise and frantest (dev site). I have our developer check all the http and make sure all the links are relative instead of absolute.

Currently you don’t seem to have any DNS records for www.franchise however if you :orange: through Cloudflare, then without a dedicated certificate, www.franchise cannot work over HTTPS.

franchise. does work, just not www.franchise.