Https - noddy's guide required

[bruce (Bruce Kieffer)]

@teefers
Doug,
Thanks. I will contact the Theme developers. I do agree that they should fix these errors.

[bruce (Bruce Kieffer)]

@jchou

The only remaining warning is the one you posted elsewhere about: “You currently have TLSv1 enabled.”, which someone responded that we can’t do anything about, I guess.

@jchou
The info about this is here:

You currently have TLSv1 enabled?

[kpryce1 (Ken)]

@jabostick Thanks for this guide to remove “not secure” - I took it at snail’s pace and I seem to have got there. If I query my site I get the nice green https. Are there any other checks I can do as, of course Chrome has not yet changed to “not secure”

[kpryce1 (Ken)]

@jabostick Ah, I see I have given you false credit and it was actually ben’s guide. As per @bruce I did a check on his padlock recommendation. The results said “Force HTTPS - Your webserver is forcing the use of SSL.”; " Valid CertificateYour SSL Certificate is installed correctly, with nice green tick". “Domain Matching”. So I guess I’ve succeeded without paying and “arm & leg” to Goddady.
@ben My check on padlock says the SSL expires in 90 days - do you know if this is a quick one-click to renew in Cloudflare?

[bruce (Bruce Kieffer)]

I wrote to the two theme developers regarding the mixed content errors I was getting with their themes. Both of them promptly issued theme updates which solved the errors. Thanks to both of them!

[ben]

@kpryce1

My check on padlock says the SSL expires in 90 days - do you know if this is a quick one-click to renew in Cloudflare?

if you’re using CloudFlare then they will automatically renew the certificate for you — you don’t need to do anything

[svsmailus (Simon)]

Pardon my ignorance, but I had assumed https was only needed for websites that people logged into. If your site only displays information (which many do), why is https necessary? Will browsers make this distinction?

[teefers (Doug Bennett)]

Not true. Big big push the last few years to secure the entire internet. Most search engines have been reducing your SERP ranking for not using SSL for a while now. Back in September Chrome, the most popular browsers started warning users any site that had any input field at all (even a simple mailing list signup) that the site was not secure.
Now in July, every non-HTTPS site will get that warning.

Effective July 2018, Google’s Chrome browser will mark non-HTTPS sites as ‘not secure’

If you’re not using SSL on your site(s) yet you’re running out of time. It looks like with the release of chrome 68 scheduled for July release sites accessed as HTTP, not HTTPS will be marked as not secure right in the address bar. Now you get that message only if you’re accepting users input. This message will affect your bounce rate.

[kpryce1 (Ken)]

@ben Thanks for that ben, I can now rest easy. Got to say though that this problem is going to cause a lot of RW users, heartache. Whilst I followed ‘mostly’ what your video outlined there were some slight deviations (in the process) with my Goddady sites. I intuitively knew what to do and got the desired result nevertheless. Don’t think we’ve heard the real howls of anguish yet.