Advice Needed

G’day Steven,

It can be just waiting for Cloudflare to kick in with a valid certificate. However, I’ve heard a few times that the Cloudflare plugin messes things up, so try deactivating that and setting HTTPS detection to HTTP_X_FORWARDED_PROTO.

https://ssl.webaware.net.au/https-detection/

If that’s not it, please post a link to an page with errors. I can’t diagnose anything very well without a link.

cheers,
Ross

Right, I added this new page with the aid of the HTTPS plugin, which allows for chosen pages to be enabled for ssl.

It’s down in the footer menu so as not to be conspicuous and is called ‘test for ssl’.

The website itself is a soft adult website:
HERE

Any help would be most appreciated!

G’day Steve,

Some of the images loaded on that page come from other websites that don’t have valid TLS certificates. Those alone are generating a bunch of warnings. The only solutions for those are to fix the certs on those sites, or remove the images from your site.

You also have a copyright seal loaded over http. If you know where that’s set, you should be able to edit it and change the URL to https. It looks like it’s in a text widget. Changing the fixer mode to Content would fix that one, but you might as well fix it at the source by editing the widget.

You can see what is causing your insecure content warnings in your browser console, or in an online test tool. Here’s a summary:

https://ssl.webaware.net.au/testing/

cheers,
Ross

• This reply was modified 7 years, 9 months ago by webaware.

Hmmm, I’m not so sure – if that were genuinely the case, why does the page (with nothing on it) give the same https error and refuse to load over an ssl certificate?

I’ve had full ssl certificates in the past, and admittedly had to use ‘where’s my padlock’ before to remove the mixed content, but to not even load up is a whole new ball game!

I’m going to try something else first – I’ll keep you up to date.

Ok, I got it (sort of) sorted by opening a new Cloudflare account. I don’t really believe that the Page Rules tot up to three PER ACCOUNT, and sure enough I’ve had no problems so far.

So now we come to a load of insecure content.

Having crashed and restored my website many times over the last few days, how would you suggest that I change the https:// to https:// without the aid of a safety net?

Got it sorted.

Turns out that there were only a couple of images needed fixing, and I’ll get those fixed up tomorrow after a good nights kip.

All the errors on chrome search console have no effect whatsoever, as bourne out by many advisors, and it looks like it’s google’s final attempt to piss people off before getting ssl sorted.

All sorted as I mentioned earlier, and thanks for your help!

Excellent, well done! And best of luck with the sites.

cheers,
Ross