Minify CSS Causes Chrome Mixed Content Warning

  • Resolved brenthutto

    (@brenthutto)


    7 years, 3 months ago

    Today I used my Let’s Encrypt SSL to start enforcing HTTPS on my new WordPress site I created a week ago. After getting all the correct settings enabled, it worked except that the Chrome browser was showing warnings about insecure scripts.

    I used the Chrome devtools to identify 18 calls for fonts that were being made with HTTP: by my theme (Katib Writers by Themeseye, if it matters). By a process of elimination I found that turning off Minify CSS in the SG Optimizer corrected the issue.

    Don’t know if it’s particular to that theme or my site in some way. But at the moment I can run all the optimization features except /Frontend Optimization/Minify CSS Files. That one causes my site to fail Google’s mixed content detection. The problem is reproducible by turning Minify CSS on and off.

    Unfortunately I can not say whether this is attributable to the newest update of SG Optimizer. I did not turn on HTTPS until after the update was installed.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    7 years, 3 months ago

    Did you enable force HTTPS in the SG Optimizer? After that did you try fix insecure content option that will appear?

    Thread Starter brenthutto

    (@brenthutto)

    7 years, 3 months ago

    This was my first time enabling HTTPS so I may not remember the sequence exactly. But yes, I used the SG Optimizer “Enable HTTPS” setting to do it, although I think first I had to set my Let’s Encrypt to be a Wildcard.

    After having problems I did go back and turn on the “Fix Insecure Content” setting but I may have tried a couple other things before that, can’t remember for sure.

    I was still getting something like 17 of the red-flagged (in Chrome’s Inspect Elements) HTTP references in font-loading requests. I was going to try a different plugin for fixing insecure content but when I turned off SG Optimizer those warnings went away.

    That’s when I turned SG Optimizer back on and tried flipping each setting on and off until I identified that Minify CSS Files was the one causing the mixed content.

    Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    7 years, 3 months ago

    Please, email me admin logins for your site at hristo.p [at] siteground.com. That’s speciffic to your site and I won’t be able to fix it withoug lookin into it.

    Thread Starter brenthutto

    (@brenthutto)

    7 years, 3 months ago

    My issue was quickly solved by SiteGround support. Wasn’t actually the Minify CSS at all.

    Thanks.

    • This reply was modified 7 years, 3 months ago by brenthutto.
    • This reply was modified 7 years, 3 months ago by brenthutto.
Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Minify CSS Causes Chrome Mixed Content Warning’ is closed to new replies.