Current Status of EasyApache 4
Last modified: October 25, 2022
Overview
This document lists the current status of features and known bugs in EasyApache 4. EasyApache 4 is stable as of cPanel & WHM version 58.
EasyApache 3 to EasyApache 4 Migration Status
The following lists the known bugs in the EasyApache 4 migration script and their status:
-
Have EasyApache 4 migration script call the CloudLinux migration script when needed.
Implemented in cPanel & WHM version 58 with CPANEL-7356. The EasyApache 4 migration script now calls CloudLinux’s migration script on CloudLinux systems when you upgrade to EasyApache 4.
-
Support the
--revert
flag in CloudLinux’s EasyApache 4 migration script.Implemented in cPanel & WHM version 58 with CPANEL-7504. We now support the
--revert
flag in the EasyApache 4 migration script on CloudLinux systems. -
Add exit codes to migrate script per CloudLinux.
Implemented in cPanel & WHM version 58 with CPANEL-7534. We added exit codes to the EasyApache 4 migration script. These codes allow third-party developers to register failures and make programmatic changes.
-
Add basic sanity check for broken repos during migration.
Implemented in cPanel & WHM version 58 with CPANEL-7462. We now ensure that yum can complete actions before the system migrates to EasyApache 4.
-
Preserve EasyApache 3’s PHP version as the default PHP version when the system migrates to EasyApache 4.
Implemented in cPanel & WHM version 58 with CPANEL-7659. The EasyApache 4 migration script attempts to set the Apache PHP handler in EasyApache 4 to match the PHP handler in EasyApache 3.
-
Add migration hooks to EA4 migration script.
Implemented in cPanel & WHM version 58 with CPANEL-7922. We added support for multiple stages of hooks to the EasyApache 4 migration script. These hooks allow third parties to ensure that their plugins and settings migrate properly. For more information, read our EasyApache 4 Migration Hooks documentation.
-
Add preflight checks to the EA4 migration script.
Implemented in cPanel & WHM version 60 with CPANEL-7820. We added a comprehensive set of blockers and warnings to the migration script. Third-party integrators can also add blockers with this change.
-
Sites with the
suPHP_ConfigPath
set break during migration.Implemented in cPanel & WHM version 60 with CPANEL-7963 and EA-4772. We created the
ea_convert_php_ini
script to convert a user’s existingphp.ini
file to one that EasyApache 4 can use if the user’s PHP version uses suPHP. This conversion happens during the EasyApache 3 to EasyApache 4 migration process. This script does not currently support manual execution. -
Ensure that the EasyApache 4 migration script migrates the system’s php.ini settings from EasyApache 3.
Implemented in cPanel & WHM version 64 with CPANEL-11202 and EA-5012. The
/scripts/migrate_ea3_to_ea4
script copies the/usr/local/lib/php.ini
file to the/opt/cpanel/ea-php??/root/etc/php.d/local.ini
file and to all installedea-php
versions on your server. To reduce the chance of conflicts, the system comments out lines that resemble the following:extension=
extension_dir=
zend_extension-
The system does not adjust any other lines.
-
Migrate Apache user data includes from EasyApache 3.
Implemented in cPanel & WHM version 66 with CPANEL-12603 and EA-3991. We now migrate the Apache user data includes from EasyApache 3 to EasyApache 4. For more information, read our The EasyApache 3 to EasyApache 4 Migration Process documentation.
Feature Status
The following lists the features in development and their status for EasyApache 4.
-
Make CloudLinux™ and EasyApache 4 compatible.
Implemented in cPanel & WHM version 56. CloudLinux released support for EasyApache 4 when we released cPanel & WHM version 56. Read their documentation for more information.
-
Fix PEAR and PECL functionality.
Implemented in cPanel & WHM version 58. The WHM PECL user interface does not work in cPanel & WHM versions 11.52, 54, or 56. We fixed this in cPanel & WHM version 58. The cPanel & WHM user interfaces for PEAR work with some limitations in cPanel & WHM versions 11.52, 54, and 56.
-
FastCGI
Implemented in cPanel & WHM version 74, with restrictions. Fully implemented in cPanel & WHM version 78. As of cPanel & WHM version 74, you can use FCGId with the MultiPHP system. It is not compatible with the
mod_ruid2
Apache module or themod_mpm_itk
Apache module. For more information, read our Apache Module: FCGId documentation. -
Tomcat compatibility
Implemented in cPanel & WHM version 76. EasyApache 4 now supports Tomcat 8.5. As of cPanel & WHM version 76, you can migrate your server that runs Tomcat. However, the implementation is completely different from the EasyApache 3 version. For more information, read our Tomcat documentation.
Bug status
The following lists the known bugs in EasyApache 4 and their status.
-
DSO PHP Handler is not exposed.
Fixed in cPanel & WHM version 54. In cPanel & WHM version 11.52, the system installed the DSO handler, but did not expose it to the configuration tools. We fixed this in cPanel & WHM version 54.
-
WHM Apache configuration Include editors do not work.
Fixed in cPanel & WHM version 56. In cPanel & WHM versions 11.52 and 54, the existing configuration checks do not work properly and the system does not save edits. You must manually edit the include files to make changes. We fixed this in cPanel & WHM version 56.
-
EasyApache 4 PHP config file,
/etc/cpanel/ea4/php.conf
, not found.Fixed in cPanel & WHM version 11.52. This error first appeared in earlier versions of cPanel & WHM version 54. We fixed this in version 54.0.5.
-
Make ModSecurity® conflict with
mod_ruid2
andmod_mpm_itk
.Fixed in cPanel & WHM version 58. In EasyApache 3, an existing bug with ModSecurity2, the
mod_ruid2
, andmod_mpm_itk
Apache modules causes some tracking functionality to not work properly with per-user MPMs. We originally added a conflict to the RPMS in EasyApache 4, so that you cannot install themod_ruid2
ormod_mpm_itk
Apache modules with ModSecurity2. On June 15, 2016, we removed those conflicts. The issue with DBM files still exists. cPanel, L.L.C. cannot fix this bug, as this is a ModSecurity2 issue. For more information, read the ModSecurity bug report.