The mixed content fixer is activated, but was not detected on the frontpage.

[Mark]

Hi Brian,

on what site are you experiencing this issue? As long as the site has the green lock the mixed content fixer was not detected warning can be safely ignored.

[Sarah]

Hi there, after urgent help regarding the same issue for our business WordPress site;

The mixed content fixer is active, but was not detected on the frontpage. Please follow these steps to check if the mixed content fixer is working

I’ve been through the help guides and followed all steps but I’m receiving the same problem. Help!

Thank you!

Sarah

[Mark]

Hi Sarah,

can you provide me with your site address? Perhaps there’s an issue with your certificate, could you perform a test at https://www.ssllabs.com/ssltest?

[ruifct]

Hi Rogier, thanks a lot for you fantastic plugin.

I’ve been using it in several websites but for the first time i’m having some problems.

Can you please check if there is anything wrong at https://www.igaming-seo.com – I use the same multidomain certificate which i use, for example, in casasdeapostasonline.com

If it helps, in IE i get the following error msg when trying to open the site “The security certificate presented by this website was issued for a different website’s address.”

I’ve tried to deactivate and activate really simple ssl again but no luck.

[Rogier]

There seems to be an issue with your certificate. Please see the scan:
https://www.ssllabs.com/ssltest/analyze.html?d=www.igaming-seo.com&latest
I would contact the supplier of the certificate to fix this.

Upon closer inspection the problem seems to be that the www domain is not added to the certificate. Adding the www domain should resolve the issue.

[ruifct]

You were right, as usual! Problem solved. Cheers

[Anat]

Hi there,
I’m facing the same issue – The mixed content fixer is activated, but was not detected on the frontpage.
Following the instructions, I view page source and ensure I have data-rsssl=1 there. It is.
However, the https is still red and the website is considered still to be unsecured.
I have WP Rocket and I cleared cache.
This is not the first time I’ve used this SSL plugin and it usually works great so hopefully we could figure this one out too.

Thanks in advance,

[Rogier]

Did you run a scan on SSLlabs? the red https usually means the SSL certificate is not valid.

[RAIANE MACHADO]

Please help.
Obtain the following error “The mixed content fixer is enabled, but it was not detected on the frontpage. Follow these steps to verify that the mixed content broker is working. Instructions ”

URL: https://dwcred.ml/

[Mark]

Hi Raiane,

the site doesn’t use a valid certificate (see https://www.ssllabs.com/ssltest/analyze.html?d=dwcred.ml&ignoreMismatch=on&latest). To fix this, you can install an SSL certificate that is issued by a certified certificate provider like Comodo or Let’s Encrypt. Really Simple SSL is not a certificate itself but a tool to configure your website for SSL, it cannot obtain or install a certificate for you.

Mark

[Michal Švéda]

Hi, I have a problem with my site: https://www.stavebniny-stupka.cz/

I have a vaid SSL certificate, but theres still info: The mixed content fixer is active, but was not detected on the frontpage. Please follow these steps to check if the mixed content fixer is working. Instructions

I-ve tried the instruction, but nothing is working.

[Rogier]

As per step 2: “Check manually if the mixed content fixer is active”, I did this, and can see it’s active.

[Brian Harness]

Hello,

I just purchased the pro version and experiencing the same problem.

I called my hosting to make sure everything is installed properly and it is, I also did the labs test and it was fine as well. Can someone please help with this.

Domain is http://www.keysolutionsus.com

[Rogier]

Hi Brian,

There is no valid SSL certificate on your site. Please check your site in https://ssllabs.com/ssltest and you will see there is a common name invalid error.

Your hosting company should be able to rectify this.

[Brian Harness]

Hello,

Thank you so much for your reply. Is there something that I may be doing wrong because on the test I’m getting an A. I type my web address as http://www.keysolutionsus.com and this is because this is how it was added on the SSL

[Rogier]

Ah. That explains it. Your WordPress website has as site_url the non www domain, so WordPress will redirect to the non www, which does not have a valid certificate.

The best practice solution is to add the non www domain to your SSL certificate.

As alternative you can add

update_option( 'siteurl', 'http://www.example.com' );
update_option( 'home', 'http://www.example.com' );

(change example.com to your own domain)
to your theme’s functions.php, then add a redirect to www to force all requests in the .htaccess to the www domain, as described here:
https://really-simple-ssl.com/knowledge-base/avoid-landing-page-redirects/

[Brian Harness]

I really appreciate your help and your knowledge!

I just got off the phone with hosting and they stated the same thing which i see now. What I have done that I think should fix is I went and deleted the www off my ssl and added without that.

They said this should work is this true? I was about to try it.

[Brian Harness]

I have changed the SSL to reflect the non www version and I have deleted the www version. Now what would you suggest?

[Rogier]

When I look here at the scan it’s still only valid for the www domain:
Valid: https://www.ssllabs.com/ssltest/analyze.html?d=www.keysolutionsus.com
Invalid: https://www.ssllabs.com/ssltest/analyze.html?d=keysolutionsus.com

Why don’t you add both www and non www? That is the generally accepted method of implementing SSL, and would solve your issue.

[Brian Harness]

That solved the problem.

I seriously really do appreciate you responding each time. Do you have donate page? If this is how support is I would love to donate and keep it going

[Rogier]

Thanks, appreciate it!
https://www.paypal.me/reallysimplessl

Or a review is also great 🙂
https://wordpress.org/support/plugin/really-simple-ssl/reviews/

[Brian Harness]

But what about both? Review and Tip!

Have a great Night!

[minnu]

Hello,

I have been getting this error “The mixed content fixer is active, but was not detected on the frontpage. Please follow these steps to check if the mixed content fixer is working”. I have done pretty much everything in the listed instructions.
A scan on the https://www.ssllabs.com/ssltest/ gives an A and “Warning: Inconsistent server configuration”
What do I do?

Thanks in advance!

[Rogier]

Hi Minnu,

If you get such an error on the scan from SSL labs, I would recommend to contact your hosting provider (assuming they installed the certificate for you), and show them the scan results. They should know what to do.

[Jimmy]

Same issue. When I launch the page the pad shows a short time after it turns grey with an exclamation point on it.

Please help!

[Mark]

Hi Jimmy,

that means that some resource is still loaded over http://. To find the exact cause of this issue you can follow this guide: https://really-simple-ssl.com/knowledge-base/how-to-track-down-mixed-content-or-insecure-content/

Mark

[Sunny]

Please, can you tell me the reason my website is not showing the Green Secure icon. I have deactivated all of my plugins but none seems to be conflicting with Really Simple SSL.
the SSL labs show the following stats
https://www.ssllabs.com/ssltest/analyze.html?d=core-expert-tutors.co.uk

Will really love you reply as soon as possible.
Thanks

[Coly]

Hello im having the same problem with my SSL.

The following error keeps occurring and i cant sort it.
(1)The mixed content fixer is activated, but was not detected on the frontpage
(2)all I see is my connection is not private……
Please this my site http://exposort.com
could you help me to check it please I have no joy……

[Mark]

Hi,

there’s one image coming from an Elementor stylesheet (https://www.core-expert-tutors.co.uk/wp-content/uploads/elementor/css/post-52.css?ver=1539820723). This seems to be the footer image that’s still using http://. To fix this, you can clear all caches the website uses or update the link to https:// manually. See https://really-simple-ssl.com/knowledge-base/how-to-track-down-mixed-content-or-insecure-content/ for a guide on how to locate mixed content issues.

[Mark]

Hi,

the site seems to be working fine now, do you still experience any issues?

[Author]

Posts