The Apache development team regularly releases new versions of Apache. We test and make the new version available in EasyApache to ensure that your software remains up-to-date.
Minor version changes do not impact functionality, but major updates may require changes to your configuration. In most cases, the EasyApache software adjusts your configuration automatically. If you use a custom configuration, you may need to make manual adjustments.
EasyApache uses Apache 2.4 by default for new installations of cPanel & WHM. To install Apache 2.2 on a new installation, you must use a custom profile.
For information on changes between Apache version 2.2 and Apache version 2.4, read our Apache documentation.
Apache 2.2 is not available on servers that run CentOS 7, CloudLinux™ 7, or Red Hat® Enterprise Linux (RHEL) 7. You must use Apache 2.4 instead.
The Apache configuration includes the following components by default:
You can use several methods to modify your Apache configuration. Read the following documentation for more information:
EasyApache provides the ModSecurity™ Apache module.
|File or directory location||Description|
|The Apache error log.|
|The primary Apache configuration file.|
|The primary Apache configuration file directory.|
|The directory that contains the include files that add content to the |
For more information on the location of the files to use to customize your Apache configuration, read our Apache documentation.
If you experience issues with Apache, we recommend that you perform the following steps to isolate the cause of the issue:
If you modified your Apache configuration file directly, create a backup copy of your configuration and run the
/scripts/rebuildhttpdconf script. If the issue resolves after the script completes, then the issue relates to a directive or custom entry inside the
If you modified any files in the
/usr/local/apache/conf/includes/ directory, create a backup copy of the files and remove all entries from the files. Restart the Apache service with the
service httpd restart command. If the issue resolves after the Apache service restarts, then the issue relates to an entry in one of the include files.