Mixed content Warnings & Errormessages

How to check if the mixed content fixer is active

If the mixed content fixer is activated in the settings, you can check on your configuration tab if Really Simple SSL detected it on the front-page. The plugin does this by checking if the homepage contains the marker comment. If not, you will get an error message:

The mixed content is activated, but the frontpage could not be loaded for verification. The following error was returned: CURLE_FAILED_INIT

Where CURLE_FAILED_INIT could also be a different error.

This notice does not necessarily mean it doesn’t work. As the plugin uses a comment in the frontpage to verify the mixed content fixer, if this comment is not there for some reason, you won’t see this message. Follow these steps to check what the problem is:

  1. If you have a caching plugin activated, the cache might still contain the websource without the marker. You can easily solve this by clearing your cache, then reload your configuration page. Really Simple SSL already clears the cache for some plugins, but not all of them.
  2. Check manually if the mixed content fixer is active. If you encounter the comment, you can ignore this notice, as it apparently works. This sometimes happens when a server or security plugin blocks the plugin from opening a page on the website. How to test:
    • Right click on your website
    • click “view source”
    • Look for the mixed content fixer marker: data-rsssl=1
    • If it’s there, the mixed content fixer is active, and you’re done. If not, go to step 3.
  3. Check if you do have mixed content on your site. If you don’t have mixed content, you can leave the error, as it seems to work. Else, go to step 4.
  4. Another plugin conflicts with the working of the mixed content fixer.

There is also another error you might get:

The mixed content is activated, but the frontpage could not be loaded for verification

If you see this error, Really Simple SSL is not able to retrieve the websource of your homepage. It is possible your server configuration forbids this. If you find the marker data-rsssl=”1″, the mixed content fixer is working, the plugin only cannot verify this.


Related Articles


  • Emily

    Thank you. This is helpful. I use Autoptimize to fix the above the fold content and its cache also cause this issue too.

    • Rogier Lankhorst

      Hi, Can you tell me what it is that is not working?

      • Martin

        Hey, I also have issues… Tried almost everything from Autoptimize, SSL Insecure Content Fixer settings, HTTPS forcing, etc…
        The Content Fixer says
        “Tests completed.

        Your server can detect HTTPS normally. The recommended setting for HTTPS detection is standard WordPress function.

        Your server environment shows this:

        [FREETDSCONF] =>
        [OPENSSL_ENGINES] => /opt/bitnami/common/lib/engines
        [OPENSSL_CONF] => /opt/bitnami/common/openssl/openssl.cnf
        [SSL_CERT_FILE] => /opt/bitnami/common/openssl/certs/curl-ca-bundle.crt
        [CURL_CA_BUNDLE] => /opt/bitnami/common/openssl/certs/curl-ca-bundle.crt
        [LDAPCONF] => /opt/bitnami/common/etc/openldap/ldap.conf
        [GS_LIB] =>
        [MAGICK_HOME] =>
        [REQUEST_SCHEME] => https
        [LD_LIBRARY_PATH] => /opt/bitnami/sqlite/lib:/opt/bitnami/mysql/lib:/opt/bitnami/apache2/lib:/opt/bitnami/common/lib:/opt/bitnami/sqlite/lib:/opt/bitnami/mysql/lib:/opt/bitnami/apache2/lib:/opt/bitnami/common/lib:/opt/bitnami/varnish/lib:/opt/bitnami/varnish/lib/varnish:/opt/bitnami/varnish/lib/varnish/vmods:/opt/bitnami/sqlite/lib:/opt/bitnami/mysql/lib:/opt/bitnami/apache2/lib:/opt/bitnami/common/lib:
        [SSL_TLS_SNI] => http://www.myurl.io
        [HTTPS] => on
        but Chrome, Firefox and Safari still show “Not secure” :/

        • Rogier Lankhorst

          Hi Martin,

          Could you e-mail me a link to your website (support[at]really-simple-ssl.com)? Then I will take a look.


  • Mahesh Patel

    Thank You SIr It was working In My site Perfectly

Leave a Comment