Title: HTTPS | CDN Issue | W3TC & DIVI Last modified: September 1, 2016 --- # HTTPS | CDN Issue | W3TC & DIVI * [Joseph Meyer](https://wordpress.org/support/users/joemeyer/) * (@joemeyer) * [9 years, 11 months ago](https://wordpress.org/support/topic/https-cdn-issue-w3tc-divi/) * Hi friends. * I have a WordPress site which has many attachments, fonts, and .js sent over to Cloudfront as a CDN via the W3TC plug-in (my theme is Divi). My client needed a SSL installed, which I did. * The problem is: even though I have +origin protocol policy+ and +viewer protocol policy+ set to “HTTPS only,” my Chrome and Edge SSL rating is still not passing( these are headers in the AWS control panel). The odd observation is that most of the CDN’s content +is+ being funneled now through HTTPS — it’s simply 8 fonts that are not changing. * Any ideas on how to fix this? * In the meantime, I’ve turned off the font-porting and localized it so I have the ‘green’ lock graphics on my client’s site. * All the best, Viewing 9 replies - 1 through 9 (of 9 total) * Moderator [t-p](https://wordpress.org/support/users/t-p/) * (@t-p) * [9 years, 11 months ago](https://wordpress.org/support/topic/https-cdn-issue-w3tc-divi/#post-7494045) * Since that is a commercial theme, we ask that you please go to their official support channel, so you can get support from the people who know it best. * [http://www.elegantthemes.com/forum/](http://www.elegantthemes.com/forum/) * Forum volunteers are also not given access to commercial products, so they would not know why it is not working properly. Other community members who may have faced your issue might be able to help you but your best bet is your product’s developer. Keep in mind we encourage you to use the official support venues, as it allows the developers to be aware of issues with their code and gives back to the community in a more robust way. * Thread Starter [Joseph Meyer](https://wordpress.org/support/users/joemeyer/) * (@joemeyer) * [9 years, 11 months ago](https://wordpress.org/support/topic/https-cdn-issue-w3tc-divi/#post-7494144) * Hi Tara! * I have posted it there, although the reason I also commented here was because: * 1) I’m not convinced it’s a theme issue; 2) I’m also not where where the problem exactly is; * therefore, I’m reaching out to many communities to see if their aggregate experience and knowledge can help guide me. 🙂 * May we still have a discussion here, then? * Moderator [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/) * (@sterndata) * Volunteer Forum Moderator * [9 years, 11 months ago](https://wordpress.org/support/topic/https-cdn-issue-w3tc-divi/#post-7494148) * Change your theme to twentysixteen. If the problem continues, then it’s not a theme problem. * Thread Starter [Joseph Meyer](https://wordpress.org/support/users/joemeyer/) * (@joemeyer) * [9 years, 11 months ago](https://wordpress.org/support/topic/https-cdn-issue-w3tc-divi/#post-7494152) * Would a theme force HTTP conversion from a CDN which exports only HTTPS? * Moderator [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/) * (@sterndata) * Volunteer Forum Moderator * [9 years, 11 months ago](https://wordpress.org/support/topic/https-cdn-issue-w3tc-divi/#post-7494153) * To deal with the “if it’s a commercial theme, go talk to them” response, demonstrate the the problem occurs with a standard WP twenty* theme, then we can talk about this. * I’ve seen a lot of problems from Cloudflare’s SSL option; I recommend installing a valid SSL cert on the site itself (using Letsencrypt) and not using a middleman for SSL. * Also, dig around to see how the fonts are being loaded. They could be enqueued via the theme’s functions.php or [@included](https://wordpress.org/support/users/included/) in a CSS file. As you find them, make sure the URLs are either https:// or just//( which should default the protocol to the site’s current protocol). * Thread Starter [Joseph Meyer](https://wordpress.org/support/users/joemeyer/) * (@joemeyer) * [9 years, 11 months ago](https://wordpress.org/support/topic/https-cdn-issue-w3tc-divi/#post-7494155) * 1) I’ll look into testing it w/ WP20 theme. * 2) Does Cloudflare = Cloudfront? * 3) I did some testing last night, and through Chrome’s console, it blocked the fonts because they came from my CNAME, which did not have “https” as a prefix. The odd part is that my .js and attachments were served (from the same source) as https. * Thoughts? * Moderator [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/) * (@sterndata) * Volunteer Forum Moderator * [9 years, 11 months ago](https://wordpress.org/support/topic/https-cdn-issue-w3tc-divi/#post-7494156) * Sorry, I misread. No, cloudflare != cloudfront * Now are you enqueuing the fonts? * Thread Starter [Joseph Meyer](https://wordpress.org/support/users/joemeyer/) * (@joemeyer) * [9 years, 11 months ago](https://wordpress.org/support/topic/https-cdn-issue-w3tc-divi/#post-7494157) * I don’t know … * [http://cdn.meysite.com/wp-content/uploads/2016/06/help.jpg](http://cdn.meysite.com/wp-content/uploads/2016/06/help.jpg) * That’s the general plug-in settings. * Any clues there? * Thread Starter [Joseph Meyer](https://wordpress.org/support/users/joemeyer/) * (@joemeyer) * [9 years, 11 months ago](https://wordpress.org/support/topic/https-cdn-issue-w3tc-divi/#post-7494158) * (Note, that is leading to a different CDN [which I need to update to HTTPS at some point] which is not causing any issues.) Viewing 9 replies - 1 through 9 (of 9 total) The topic ‘HTTPS | CDN Issue | W3TC & DIVI’ is closed to new replies. * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) * 9 replies * 3 participants * Last reply from: [Joseph Meyer](https://wordpress.org/support/users/joemeyer/) * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/https-cdn-issue-w3tc-divi/#post-7494158) * Status: not resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics