Mixed content

My browser still gives mixed content warnings

If you still get mixed content warnings, you have to track down the cause.

If the mixed content fixer is working, the Really Simple SSL fixes all images, javascript, style links, @import urls and iframes with http links. In most cases, the mixed content is caused by http links in javascript (.js) or stylesheets (.css) that were included. The mixed content fixer cannot fix these.

Read this step by step article how to track down mixed content. After you’ve tracked down the .css file or .js file, you can change its source from http:// to //, which makes it fit for both protocolls.

If you have urls in your websource causing mixed content warnings that were not fixed, while the mixed content fixer was active, please let me know which html code caused this, so I can add it to the mixed content fixer.

Related Articles

  • Disabling ssl for one page only

    The problem: services that don’t support SSL I think the best way to go is to get your entire site on SSL. But sometimes there are services that are not...
  • How to track down mixed content or insecure content

    The built in mixed content fixer in Really Simple SSL fixes all mixed content that’s part of your websource. But there are some types of mixed content that need to...
  • Plugin conflict force rewrite title Yoast

    * Update* This issue should be resolved in the 2.4 version. I left the Yoast check for now, but this warning will be removed in future versions. If you have...
  • Images not found with Photon from Jetpack

    Some websites using JetPack have Photon activated. Photon is an image acceleration and editing service, where the images are served from the WordPress cloud. In some cases, there are issues...