Installing and Uninstalling Easy Apache4 with Simple Commands

EasyApache 4 Migration can be used in cPanel or WHM version 58 or higher.

Pre-requisites –

Operating Systems –

EasyApache 4 supports the below operating systems –

• CentOS 6 or 7
• CloudLinux 6 or 7
• Red Hat Enterprise Linux 6 or 7

Note:
EasyApache 4 only supports CloudLinux in cPanel & WHM version 56 or later. This feature is a beta release.

Apache and PHP –

• EasyApache 4 only supports Apache version 2.4.
• EasyApache 4 supports PHP versions 5.4, 5.5, 5.6, and 7.0.

Settings –
If you install EasyApache 4, activate the rpm_up setting on your system as below –

• Open the /etc/cpupdate.conf file and set the RPMUP key’s value to daily.
• Go to the Update Preferences interface in WHM (Home >> Server Configuration >> Update Preferences) and set the Operating System Package Updates setting to Automatic.

Steps to Install EasyApache 4 –

Run the following command –

/scripts/migrate_ea3_to_ea4 –run

You will see the changes that will occur in the interface below –

Arguments –

The /scripts/migrate_ea3_to_ea4 script accepts the below arguments –

How to Uninstall EasyApache 4?

Note:
It’s possible to uninstall EasyApache 4 if you have migrated your system from EasyApache 3

Steps to uninstall EasyApache 4 –
Run the following command to revert from EasyApache 4 to EasyApache 3 –

/scripts/migrate_ea3_to_ea4 –revert –run

Notes:
This command reverts the system to your previous EasyApache 3 installation and configuration.
This command attempts to move the Apache files to a new location and reverts the server to the previous state. You can upgrade and downgrade as many times as you wish.

Important:

• 1. Each time a migration is performed from EasyPache 3 to EasyApache 4, the system moves the /usr/local/apache/ directory to the /usr/local/apache.3/ directory.
  • a. If the /usr/local/apache.3 is available, the system moves the /usr/local/apache/ directory to the /usr/local/apache.3.1/ directory.
  • b. If the /usr/local/apache.3.1 is available while running a migration, the migration will fail for preventing data loss.
• 2. The chance of errors increases dramatically if you migrate your system multiple times. In case you revert several times, you need to manually delete the previous /usr/local/apache.3.1 backup directory to continue. The system preserves the /usr/local/apache/ automatically.

Follow the system’s instructions.