Understanding the Inherit PHP setting in cPanel

Inherit lets a domain obtain its PHP selection from the applicable configuration higher in its directory tree or the server default. It does not necessarily mean the newest installed PHP version, and it is not compatible with enabling PHP-FPM for that domain.

01 Information to have ready

Record the current explicit version, document root and PHP-FPM status. Check the application’s compatibility before allowing a future server-default change to affect it. Ask support if you need a stable explicit runtime.

02 Check which PHP version the domain inherits

  1. Open MultiPHP Manager and inspect the domain’s current setting and PHP-FPM indicator.
  2. If inheritance is appropriate and permitted, select the domain, choose inherit and apply the change. Do not disable PHP-FPM blindly just to make the option available.
  3. Understand the effective lookup: applicable PHP information in .htaccess along the directory hierarchy can influence the result before the server default is used.
  4. Check the application’s actual runtime after the change and test its important workflows.
  5. If the resulting version is unsuitable, select an explicit supported version through the panel and retest. Keep the domain’s runtime choice documented for future migrations.

03 Confirm the expected result

The displayed configuration and effective web runtime should agree with the intended policy. Check nested document roots carefully because another domain’s configuration can affect inheritance.

04 Example: investigate a site that changed PHP unexpectedly

If a domain is set to Inherit, its effective version depends on the server or parent configuration that applies to it. Record both the selected mode and the version the website actually runs. The word Inherit is not itself a PHP version.

Compare the domain's document root and handler settings with the intended service configuration. A different domain, subdirectory or scheduled command may use another runtime. Check the application requirements before deciding whether an explicit version is more appropriate.

How should I make the change safely?

Preserve the current setting and test on a staging copy where possible. After selecting the intended version, exercise the application's important functions and inspect errors. Include uploads, database operations and scheduled work, not only the public home page.

If the selected version is unavailable or the effective runtime still differs, contact us with the domain, document root, selected mode and observed version. Do not publish a permanent diagnostic page or send an unredacted environment dump. We can help determine which supported configuration controls the request without asking you to edit server-wide files from a shared-hosting account.

Why can I not choose Inherit while PHP-FPM is active?

If inherit cannot be selected with PHP-FPM active, that is a supported limitation rather than an error to bypass. Do not paste copied handler blocks into every folder. Have support review conflicting generated configuration and use the panel’s supported runtime controls.

  • 0 Users Found This Useful
  • cpanel-whm, development
Was this answer helpful?

Related Articles

Changing the PHP upload_max_filesize limit with CloudLinux in cPanel

upload_max_filesize sets the maximum size of an individual uploaded file accepted by PHP. The...

Changing the PHP post_max_size limit with CloudLinux in cPanel

post_max_size limits the size of the entire HTTP POST body received by PHP. It includes...

Managing PHP extensions with CloudLinux in cPanel

Extensions add capabilities such as database access, multibyte text handling, image processing...

Configuring allow_url_fopen with CloudLinux in cPanel

allow_url_fopen controls whether PHP file functions can use supported URL wrappers, such as...

Configuring PHP error display and logging with CloudLinux in cPanel

PHP errors are useful for diagnosis, but displaying them on a public site can expose filesystem...