Recurrent problem: pixel.wp.com causing insecure content warning

  • Resolved wahahey

    (@wahahey)


    4 years, 3 months ago

    The Jetpack stats pixel, or whatever pixel.wp.com is, keeps causing an insecure content warning on our site. Jetpack seems to be calling https://pixel.wp.com, not https://
    This happens every few days or so, sometimes being resolved by clearing caches. But then it recurs, again and again. It is the only non-secure resource.

    I have tried disconnecting and reconnecting Jetpack.
    I have tried deactivating and uninstalling, as per Jetpack instructions.
    These actions seem to have had no effect.

    We have both website and shop set to https, redirects from non-secure to secure in the htaccess and a caching plugin that is supposed to force SSL and ensure external content is also SSL.

    Not sure what else to do, but this is driving me nuts!
    Any help appreciated.

    • This topic was modified 4 years, 3 months ago by wahahey.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Anonymous User 3392934

    (@anonymized-3392934)

    Thank you for reaching out to us about the insecure content warning you’re seeing, @wahahey!

    I visited your site, and wasn’t able to replicate this. I refreshed the HTTPS version of your site repeatedly, and it was consistently secure.

    However, I noticed that your site isn’t redirecting HTTP → HTTPS. I wasn’t redirected when visiting this:

    – https://www.divedup.com/

    or this:

    – https://divedup.com/

    I’d suggest revisiting the redirects/htaccess directives you’ve configured, as they might be missing the above URLs.

    Please let us know if this happens again. We’re happy to take another look! ??

    Thread Starter wahahey

    (@wahahey)

    Hi Mark

    Thanks so much for looking into this for me. You’ve been really helpful, revealing what was really going on. Schoolboy error – an old bookmark which went to the http version + an htaccess redirect which was configured to send everything https://www. to https://www, but not non-www to https.

    So the problem was not Jetpack at all, the pixel was just the canary in the coalmine.

    In case anyone else has the same problem the following page was very helpful:

    https://htaccessbook.com/htaccess-redirect-https-www/

    • This reply was modified 4 years, 3 months ago by wahahey.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Recurrent problem: pixel.wp.com causing insecure content warning’ is closed to new replies.