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

  • 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...
  • Compatibility fix for Social Warfare share counts recovery

    *  EDIT * This fix is not needed anymore, as Warfar plugins has integrated this fix in their plugin.  If you are using the Social Warfare share counts recovery plugin to...
  • Parts of my site not loading

    Did you install Really Simple SSL on your site, and now some images, stylesheets, or external servcies are not loading? When a site is requested over the SSL protocol, the...
  • Hyperlinks to external urls getting replaced to https

    There are two situations where a normal hyperlink to an external url could get replaced to https Website domain is part of the external domain When the external url is for example http://domain.com.au...