Add blog for Lets Encrypt SSL and what to change for full https?

[Guest]

With the new Google Chrome 62 coming on 17th October and pretty much everyone needing to use sitewide SSL it might be worth blogging about Lets Encrypt SSL and also scripting to auto-renewing it as it only runs for 90 days. I know the lets encrypt forums have people there listing Cron jobs to do it.

[Traumflug]

Turning on SSL is a task to be done with server configuration tools, thirty bees can't help with this. Once it works, one simply turns it on in Backoffice -> Preferences -> General.

[Guest]

@traumflug I know it's a server configuration doing the initial setup but the reason I stated a blog about it is guidance for merchants for when Google suddenly states their website isn't secure if they weren't already on https.

FYI It's not just turn it on in preferences -> General. The process is: Get SSL and get hosting company to apply it Update the .htaccess for the rewrite to https from http. Update all of your http links to https on the website - you'd have checked this out previously though for third party linked scripts that you need to find out the equivalent https for. Create a new website under Google Search Console for https and submit your new sitemap Link your Google Analytics to this new account and change the http to https in the various Analytics locations Submit the new sitemap to Bing (I don't know about the other search engines) Update your Cron job to ensure it's generating the https version of the sitemap Update your robots.txt to point to the https of the sitemap Where possible update all local directories etc to reference your new https links Update all your social media for https, including your Pinterest, Instagram, Facebook, Google+ and whatever. Watch your search console for issues that may arise...

There's a number of reasons not everyone is on https, one of these is some shared servers don't allow keep-alive and as https is slower than http there's a distinct performance impact by using https on those sites. I know http/2 mitigates the need for keep-alive but most hosting companies don't support this. Also as you know the handshaking for https is much slower than http. This is another reason for updating backlinks to https so your server doesn't have to waste time redirecting from http to https unless necessary.

For some people migrating from a PrestaShop site they might well be on http from the outset. As Thirty Bees is not just about the software but also the community, I figured it'd be a nice blog to help out merchants get ready for the Google Chrome update.

[Traumflug]

Modern flavor of communications? A poster answers to the solution, but also deletes it before one can read it? Also removes the question, so there's no hint on what the actual issue was? Funny.

No, it's no fun. I should stop trying to help people. These people make an idiot of me.

[JamesBlond008]

His Question is really interessting. Its kind of Mysterious. I love riddles like this :D

[MockoB]

@Traumflug I don't want to offend you but you are not exactly helping type person. You always have opinion and in most cases it is sarcastic answer without bringing any solution to the one asking. Take for example the current topic. I want to thank you for the contribution to thirty bees project but little more humanity in your answers would be welcome. Don't forget that not everyone here is developer, many of us are ignorant merchants which would love to learn how to make their shops better. And giving idea about blog topic is not that bad I think, I know how hard is to find decent and useful topics to write.

[Traumflug]

D'oh. Describing the steps to be done is sarcastic and of little help. Thanks for the lesson.