After installing a WordPress plugin – WP Health, it’s reminded that PHP5 had no longer been supported since late 2018, thus there may be risk in all WordPress websites.

Issue

Since removing PHP5 (retrospectively known that it’s not necessary), and installed remi’s repository’s PHP72, some WordPress sites could not be accessed with message: “Internal Server Error. The server encountered an internal error or misconfiguration and was unable to complete your request.” Then using VirtualBox’s snapshot to roll back and finally got every site back to normal.

However, using re-check configuration of Virtualmin to see if there’s anything need to follow up, it’s known that mod_actions of Apache wasn’t enabled. Then after enabling mod_actions by uncommenting the following:

LoadModule actions_module modules/mod_action.so

in /etc/httpd/conf.modules.d/00-base.conf, something weird that instead of executing php page, these pages were downloaded. Some members on forums suggested that the following in /etc/httpd/conf.d/php.conf should be commented out:

SetHandler application/x-httpd-php

This really solved the problem of not executing php pages, but another weird thing happened. Some other websites couldn’t be accessed again with message: 500 Internal Server Error.

Solution

1. The permission of some html directories all granted to 775 and changed owner as apache.
2. In Virtualmin, Server Config -> Website Options -> PHP script execution mode must select FPM if mod_fpm is installed and enable.

Tricks

Before comment out SetHandler application/x-httpd-php, directory permission was not a problem. What and how does something change the permission or why is the permission of html directories should be further granted to eliminated 500 Internal Server Error?

Config

• WordPress 5.1
• Virtualmin 6
• PHP7.2 remi
• CentOS7

The post PHP 7 & Related Issues appeared first on LarryLai.

Background

After installing WP Health, it’s shown that both MariaDB 5 (a default replacement of MySQL for CentOS7) and PHP5.6 are obsolete, i.e. no more formal support and no security patches will be released. It’s suggested to upgrade at least to MariaDB10 and PHP7.

Apart from security and support concern, it’s known that PHP7 has better performance than PHP5.

Issue

After upgrading, either the Virtualmin has problem in displaying submenu on the left panel or there’re “Internal Server Error” on some WordPress sites. It’s found out that during yum update MariaDB, it’s required to remove the old MariaDB5, however, for packages dependency needs, yum will at the same time remove Postfix and Virtualmin-base. If these 2 packages are reinstalled after upgrading to MariaDB, then WordPress has problem.

Solution

Use rpm -e –nodeps to skip removal of Postfix and Virtualmin-base.

Tricks

After removal PHP5.6, list out all the related packages, e.g. php-mysqlnd, php-gd, etc. depending on my case, there’re some others. All these have to be reinstalled after installing PHP7.2 base package.

For upgrade of PHP7, never upgrade to the lastest PHP7.3 as some of the PHP packages do not have PHP7.3 compatible rpm, only have PHP7.2 compatible rpm. There’re many CentOS PHP7 upgrade info. on the web, but some are not good, after try and error, I use TecAdmin.net’s advice and got no problem.

Config

• CentOS: 7.6
• Virtualmin 6.06
• WordPress 5.1
• MariaDB: 10.1

The post Centos7 Virtualmin Upgrade PHP7 MariaDB appeared first on LarryLai.

The post McDonald’s New Seats appeared first on LarryLai.