Mixed content Plugin conflicts

Known plugin compatibility issues

Sometimes Really Simple SSL doesn’t work too well with other plugins. Most of the time this is caused by another plugin blocking the mixed content fixer. We know of compatibility issues with the following plugins:

WP Social SEO Booster (hasn’t been updated in three years, so wouldn’t recommend to use it anyway)

USM Premium (USM support appears to have a fix for this, or they may fix it in the next update)

Genesis Toolbar Extras, thanks to Jon Burr for reporting it

SEO WordPress (Currently under investigation)

Deactivating these plugins should resolve your issues with Really Simple SSL.

If you encounter any plugin compatiblity issues, please share this the comments. In most cases, the problem is that the output buffer is used in a way that is not compatible with Really Simple SSL. For example, in the case of USM, the output buffer wasn’t started properly in some cases, which caused the flushing of the output buffer to flush the Really Simple SSL output buffer.



Related Articles

  • Troubleshooting with Really Simple SSL

    If you are experiencing problems which you don’t have when Really Simple SSL is deactivated, there are some steps you can do to track down the cause. Clear your browser...
  • 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...
  • 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...


  • Jon Burr

    Genesis Toolbar Extras breaks the mixed content fixer, preventing the line “data-rsssl” from showing, and causing the insecure alert in Chrome.

    • Rogier Lankhorst

      Hi Jon, thanks for reporting it!

Leave a Comment