Page tree
Skip to end of metadata
Go to start of metadata

For cPanel & WHM version 64

What are the functionality changes to Apache 2.4?

Apache 2.4 introduced changes to Apache's configuration file. Apache 2.4 also introduced, renamed, and removed several directives.

cPanel & WHM servers use the AdvConfig feature to manage the Apache configuration file (httpd.conf). To give our customers the best experience with Apache 2.4, we updated the AdvConfig feature to handle Apache upgrades and downgrades.

What is the cPanel and Apache page that I see at my domain?

This is a placeholder page for Apache. Ask your web host to properly configure VirtualHost in Apache's configuration file.

Why does Apache restart every 10 minutes?

This is normal behavior. The cpanellogd daemon sends Apache a SIGUSR1 (graceful restart) signal every ten minutes so that it can rotate logs and process statistics.

How can I add or remove support for features like PHP or Java server pages to my Apache webserver?

EasyApache adds or removes support for features from the Apache webserver.

  • EasyApache 3
    • Access EasyApache 3 through WHM's  EasyApache 3 interface (Home >> Software >> EasyApache 3).
    • You can also run EasyApache 3 from the command line with the /scripts/easyapache script.
  • EasyApache 4

Why does Apache crash with this error: [notice] child pid x exit signal File size limit exceeded (25) ?

This usually means that a log file has grown too large for the system (generally 2 GB). To address this issue, run the /scripts/biglogcheck script.

If you have extremely large or active sites that reach this limit quickly, you may wish to upgrade to a 64-bit OS, which increases your site's maximum file size to 4 TB. You may also wish to disable logging for that site. If you disable logging, you will gain a small performance increase and avoid this error.

Note:

If you disable logging, you cannot generate statistics for the domain.

Why did I receive the HTTP Error code: 206 Partial content error message?

To find out why you received this message, perform the following steps:

  1. Log in to the server as the root user via SSH.
  2. Run the tail -f /usr/local/apache/logs/error_log command.
  3. Refresh the page in your web browser. You will see an error message in your SSH session.

What are Apache dummy requests?

Apache occasionally needs to start processes that listen for new connections. To do so, Apache uses dummy requests.

  • A dummy request is an HTTP request that Apache sends to itself.
  • When Apache uses dummy requests without SSL, these requests appear in access log files with the remote address set to the local host (127.0.0.1 for IPv4 or ::1 for IPv6).
  • These dummy requests are a normal part of Apache's functionality, and you can ignore them.
  • On a lightly loaded server, WHM's  Apache Status interface (Home >> Server Status >> Apache Status) frequently shows a high number of dummy connections. This occurs because the feature shows the last request to a worker slot, which is typically a dummy request that starts a process so that the process can repeat.
  • Apache's dummy requests cannot use SSL. Servers with hosts that use SSL can receive noise in the log file that resembles the following example:

    [info] [client ::1] Connection to child 6 established (server localhost:443)
    [info] Seeding PRNG with 656 bytes of entropy
    [info] [client ::1] SSL library error 1 in handshake (server localhost:443)
    [info] SSL Library Error: 336027900 error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol speaking not SSL to HTTPS port!?
    [info] [client ::1] Connection closed to child 6 with aborative shutdown (server localhost:443)

How do I customize the way that Apache treats certain types of files?

The mod_mime Apache module customizes how Apache treats certain file types. The AddHandler and AddType directives tell Apache how to treat particular file extensions.

 

cPanel & WHM with PHP

How do install PHP 7, and what changes do I need to make?

Important:

PHP 7 is only available on systems that run EasyApache 4 and run cPanel & WHM version 54 or higher.

To install PHP 7, run the yum install ea-php70  command on the command line. For more information, read our How to Locate and Install a PHP Version or Extension documentation.

To use PHP 7 with EasyApache 4, assign PHP 7 to your desired users in WHM's MultiPHP Manager interface (Home >> Software >> MultiPHP Manager). You can also set the system default to PHP 7 in this interface. 

Note:

Make sure that the PHP programs and scripts that you plan to run are compatible with PHP 7.

Will PHP run without problems?

This depends on which third-party extensions that you need and which version PHP that you wish to use.

We document incompatibilities with third-party extensions in the  EasyApache 3 interface (Home >> Software >> EasyApache 3) for systems that run EasyApache 3.  The system performs dependency resolution before EasyApache 3 generates the build. This practice skips incompatible extensions, even if a user ignores the warning in the interface.

In EasyApache 4, the system uses RPMs to install your desired features. The RPMs have their dependencies and conflicts built in, and will notify you if your desired package is not compatible with something that you already have installed. 

Which PHP version displays on the end user's cPanel account?

The system's default PHP version displays in the end user's cPanel account interface.

How do I install and activate Zend Optimizer?

The root user can install and activate Zend Optimizer with the /scripts/installzendopt script.

How do I install ImageMagick?

To  install and activate ImageMagick for EasyApache 4, run the following commands as the root user:

yum install ImageMagick ImageMagick-devel
yum install pcre-devel 
scl enable ea-php56 "pecl install imagick"

Note:

In this example, replace 56 with your server's PHP version.

How do I change the maximum connections for HTTP?

Change the value of the Max Clients setting in WHM's Global Configuration interface (Home >> Service Configuration >> Apache Configuration >> Global Configuration).

Set the Max Clients setting's value equal to or lower than the value of the Server Limit setting.

Why do I receive a "Not Supported" message when I attempt to access my website with a mod_userdir-style URL?

Apache's mod_userdir module allows for visitors to access a user's website via a URL that contains that user's username. For example:

http://host.example.com/~username
http://example.net/~username   
http://192.168.0.20/~username

This method to access websites causes a conflict with the mod_ruid2 Apache module. Apache's mod_userdir module will not function if Apache's mod_ruid2 or mod_cgi modules run on your server. Apache enables these modules by default when you install EasyApache4. 

To configure you system to allow access to websites via a mod_userdir-style URL, perform the following steps:

  1. Navigate to WHM's EasyApache 4 interface (Home >> Software >> EasyApache 4).
  2. Select the profile that you wish to use in the Profile stage and click Customize
  3. Set the mod-cgi and mod_ruid2 modules in the Apache Modules section to Uninstalled.
  4. Install EasyApache with the new profile.
  5. Set your PHP handler to use suPHP in WHM's MultiPHP Manager for WHM interface (Home >> Software >> MultiPHP Manager).

You can now access your website via a mod_userdir-style URL.

Additional documentation