Recent Update Creating “connection not private” error on some iphones

If you see something like common name invalid, it’s always an issue with the SSL certificate. If it’s only on mobile phones it is probably a certificate chain issue:
https://really-simple-ssl.com/knowledge-base/ssl-working-desktop-not-mobile-android-devices/

You can test this by running a scan on ssllabs.com/ssltest. Your hosting company should be able to help you with this.

Yes, but I am quite confident that this just happened right after I applied the most recent Really Simple SSL update. also the ssllabs reports shows a grade of an “A”, all perfect. And the hosting company checked the configuration up and down. Finally, all other sites that do not run your plugin are still fine. It is literally only the 4 sites that I have applied the updates to that this is happening. I see the update edited my htaccess documents – all of them – and that may be the cause. However I examined those too and nothing seems to be wrong. On one site I also replaced the new version with a slightly older version of the plugin and it did not reverse the issue.

so since I have several sites under the same UCC SSL and the only site that are now not working are the ones that I updated with your plugin, and noting everything else is still all clear, is there ANY chance that it is the plugin update? all signs really seem to point to this here, wouldn’t you say?

I am happy to pay for a license to get full support here. especially if that can ensure that you look into this just a tad bit for me. it is kind of urgent and I have spent 48 hours now trying every other possible solution since I applied this update. I got word of this issue within 15 minutes of applying the update and have had dozens of reports since. However nothing on any other non-WP site running on same server / SSL.

thanks very much for your rapid response. again, if I need to buy a license to get some urgent and detailed support just say the word! I figured this may be more widespread of an issue by now.

Chad

Oh, and android devices seem to be fine. so far only reports of some iphones are the issue. again only on sites that had the plugin update applied too. the rest seem to be fine.

Really Simple SSL doesn’t do anything to the SSL certificate, the plugin checks for a valid SSL certificate and then changes your home- and siteurl to https://, updates your internal and external src=”” links to https:// and adds a redirect to https://. While I understand it seems like Really Simple SSL caused this, I can assure you that’s not possible since it doesn’t alter the certificate.

One thing I see when checking your certificate is that the www domain has a certificate, but the non-www domain doesn’t. See https://www.ssllabs.com/ssltest/analyze.html?d=www.liveatdevonshire.com and https://www.ssllabs.com/ssltest/analyze.html?d=liveatdevonshire.com. This can result in the common name error when users visit the non-www site.

To fix this, you can also install a certificate for all non-www domains. That will likely solve your error. Another option is to bypass the non-www domain by adding a redirect to https://www for all domains, however it’s considered best practice to have both the www and non-www covered by the certificate.

Before moving to SSL, this issue wasn’t apparent because the site wasn’t visited over SSL, that’s likely why it seems related to Really Simple SSL.

Mark

• This reply was modified 5 years, 11 months ago by Mark.

Thanks again Mark!

My concern is that the SSL has been installed and working just fine for all sites for quite a while now. The just at the end of last week, I updated the plugin and then I started to get warning messages as if some internal referral process has been changed or interrupted.

So I would agree with everything you said if I had just installed the SSL. but it has been working great for a few months now and then I update the plugin and literally within a few hours I get reports on JUST the sites I updated the plugin with.

I understand that there seem to be some other technical reasons that would create issues should this have all just been installed, but like I said, it was fine literally until I updated the plugin. If this had happened just to one site, I could see how there could be many things affecting thing. However when I just update 4 sites’ plugins and all 4 sites get errors reported within a few hours and all sites I did not update are just fine, I really can’t believe that something else coincidentally happened at the same time.

Now you may surely wash your hands of this – I can’t force you to help me of course. I was hoping my offer to pay for tech support may influence your decision a bit. However at this time I am not convinced that something odd happened to just 4 sites randomly right at the same time that I updated the plugin.

I guess I am just stuck for now. Thanks for your time!

Hi @wwc96,

The issue here is that your SSL certificate does not support the non www domain. If you are sure it was working before and the SSL certificate has not changed, you must have had a custom redirect in place, bypassing the non www domain.

The only way I can think of where the plugin update could have caused this redirect to disappear, is if it was inserted in the core WordPress .htaccess rules or in the default Really Simple SSL .htaccess lines. As both WordPress and Really Simple SSL might rewrite these lines, this might be the cause.

If you want to customise the Really Simple SSl redirect, it’s best to do it following these instructions:
https://really-simple-ssl.com/knowledge-base/avoid-landing-page-redirects/
But keep these custom lines outside the Really Simple SSL comments.

This is also the solution you can use to resolve this. Or you can add the non www domain to your certificate, which is the recommended solution.

If you have any questions, let us know.