Skip to content

Knowledgebase

Adding an EasyApache PHP extension without changing every domain

cpanel-whm, domains-dns

EasyApache PHP extensions are installed for specific PHP versions. An extension present for one runtime may be absent from the version used by the failing website or its scheduled CLI task.

Check access and requirements

Collect the application’s exact missing-extension error and effective PHP version. Record the current package set and confirm the requested extension is supported by the application and server stack.

01 Add an EasyApache PHP extension without changing every domain

  1. Open EasyApache 4 and customise the currently installed configuration.
  2. Search the PHP Extensions section for the required extension and filter by the actual runtime version.
  3. Select the necessary package and review dependencies or conflicts. Avoid enabling unrelated modules simply because their names look similar.
  4. Inspect the final install, upgrade and removal list, then provision the approved change. Wait for a completed result.
  5. Verify the extension in the application’s actual web runtime and repeat the failing operation. If a cron task is involved, check its specific PHP binary separately.

02 Example: inspect the extension in the selected CLI runtime

Replace /path/to/selected/php with the verified executable used by the affected scheduled task. The example checks mbstring; substitute the actual required extension name when appropriate.

Code or configuration example
/path/to/selected/php -v
/path/to/selected/php --ri mbstring

The first command identifies that executable’s version. The second reports the named extension’s configuration when it is available in that CLI environment. If it is absent, compare the extension package and loaded configuration for this exact runtime before changing another PHP version.

This does not establish what the website loads. Verify the web runtime through the application’s supported diagnostics and repeat the original web operation separately. Remove any temporary public diagnostic file after the check.

Confirm the expected result

The required function should become available to the intended runtime and the application should complete the original task. Remove temporary public diagnostic scripts after verification.

Resolve setup problems

If the extension is unavailable, consult the supported vendor package or PECL workflow for that exact runtime instead of copying a binary from another server. Some errors concern a disabled function, missing system library or wrong PHP version rather than an uninstalled extension.

Does installing an extension activate it for every PHP version?

No. Verify each runtime that actually needs it. Web and command-line processes can load different configurations even when their version numbers appear similar.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support

Powered by WHMCompleteSolution