Title: CSS Issue When Switching to HTTPS
Last modified: December 6, 2017

---

# CSS Issue When Switching to HTTPS

 *  Resolved [knowitallninja](https://wordpress.org/support/users/knowitallninja/)
 * (@knowitallninja)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/css-issue-when-switching-to-https/)
 * I have just started to use my CloudFlare Flexible SSL cert (always used CloudFlare,
   didn’t no I could use SSL with it). This has mostly worked brilliant but with
   one very big issue with Autoptimize.
 * When I have Optimise CSS Code activated the CSS does not display. It is just 
   plain black text on white background. Deactivating this option leaves the site
   working perfectly with CSS and all.
 * I have purged the cache and purged the CloudFlare cache (just in case).
 * One test I just ran, if I have the Optimise CSS Code activated but remove my 
   MaxCDN base URL, then the CSS does load fine.
 * I have tried the base URL as http// https:// & //
 * All seem to have the same problem. Any ideas?

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/css-issue-when-switching-to-https/#post-9757981)
 * can you set the base url to [https://<your](https://<your) maxcdn url> and then
   run a test on [https://webpagetest.org](https://webpagetest.org) and post the
   resulting URL here so I can review the result?
 * frank
 *  Thread Starter [knowitallninja](https://wordpress.org/support/users/knowitallninja/)
 * (@knowitallninja)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/css-issue-when-switching-to-https/#post-9757986)
 * I’m really sorry Frank. I just set the CDN to https:// and it has now worked.
   I promise I tried it twice (along with all the other options).
 * Thank you as always for the quick response.
 *  Thread Starter [knowitallninja](https://wordpress.org/support/users/knowitallninja/)
 * (@knowitallninja)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/css-issue-when-switching-to-https/#post-9758024)
 * Not that I want to be a massive pain, but it isn’t working again. Neither is 
   the JS.
 * Here is the test result link:
 * [https://webpagetest.org/result/171206_WZ_399dbdeb6c28a9c896503db08e4c20e8/](https://webpagetest.org/result/171206_WZ_399dbdeb6c28a9c896503db08e4c20e8/)
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/css-issue-when-switching-to-https/#post-9758035)
 * weird, there’s not trace in the waterfall of any autoptimize asset being loaded.
   somehow it seems like the fact that you combine cloudflare + maxcdn is an issue,
   not entirely sure why though. but given the fact that when on cloudflare all 
   is automatically cdn’ed, you could just leave the “base cdn url” in AO empty?
 *  Thread Starter [knowitallninja](https://wordpress.org/support/users/knowitallninja/)
 * (@knowitallninja)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/css-issue-when-switching-to-https/#post-9758096)
 * Unfortunately I really want the MaxCDN to work too. I will speak to CloudFlare
   and MaxCDN about it if you feel it’s not an Autoptimize issue.
 *  Thread Starter [knowitallninja](https://wordpress.org/support/users/knowitallninja/)
 * (@knowitallninja)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/css-issue-when-switching-to-https/#post-9758189)
 * Thought I’d share with you for future reference. I had to create a shared SSL
   pullzone in MaxCDN and put the new shared ssl pullzone in autoptimize.
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/css-issue-when-switching-to-https/#post-9758685)
 * > Thought I’d share with you for future reference. I had to create a shared SSL
   > pullzone in MaxCDN and put the new shared ssl pullzone in autoptimize.
 * ah, because your old pullzone referred to you pre-cloudflare domain? that makes
   some sense. thanks for the feedback! 🙂

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘CSS Issue When Switching to HTTPS’ is closed to new replies.

 * ![](https://ps.w.org/autoptimize/assets/icon-256X256.png?rev=2211608)
 * [Autoptimize](https://wordpress.org/plugins/autoptimize/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/autoptimize/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/autoptimize/)
 * [Active Topics](https://wordpress.org/support/plugin/autoptimize/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/autoptimize/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/autoptimize/reviews/)

 * 7 replies
 * 2 participants
 * Last reply from: [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * Last activity: [8 years, 5 months ago](https://wordpress.org/support/topic/css-issue-when-switching-to-https/#post-9758685)
 * Status: resolved