Simply Fast WordPress [15] – Enabling Always-On SSL and HTTP/2 on an existing HTTP WordPress site (Part 1: Preparation)

This is a series of articles explaining how to speed up WordPress, the use of which is growing rapidly for CMS-based business sites and media sites. This time, we will explain how to implement Always-On SSL and HTTP/2 on an existing HTTP WordPress site.

Last time, we explained how to set up a new WordPress site that uses Always-On SSL and HTTP/2, first with free certificates through Let’s Encrypt in Vol 13, then with business SSL certificates in Vol 14.

However, there are probably many of you who already have your own WordPress site running. Over the next two installments, we will explain how to migrate existing HTTP WordPress sites to KUSANAGI and configure them with Always-On SSL and HTTP/2.

Along with this article, please check “Using KUSANAGI – Adding Always-On SSL and HTTP/2” for some basics on Always-On SSL and HTTP/2 and why they are necessary.

KUSANAGI version upgrade details 8.0.2-3

KUSANAGI version upgrade details 8.0.2-3

The bug fix of KUSANAGI 8.0.2-3 is done.
If you are currently using a previous version, please enter the following command as root user to upgrade to 8.0.2-3

# yum update

KUSANAGI 8.0.2-3 bug fixes

  1. Shows error while kusanagi provision

1. Shows error while kusanagi provision

CT log server will stop the registration when kusanagi provision with --email option to issue Let’s Encrypt SSL certificate in KUSANGI-8.0.2-2.
However, error messages wont output to script in this process.
This bug have been fixed in kusanagi-8.0.2-3 update.

KUSANAGI module update

The modules that composed KUSANAGI had been updated. The new versions are as follows.

NGINX 1.11.8

Use the following command to update modules.

# yum update