Confirm the server uses a supported PHP-FPM arrangement. Active LiteSpeed installations use their own PHP handling and may not expose these WHM controls. Record the current runtime, handler, memory capacity and affected shared-root domains.

1. Open MultiPHP Manager > User Domain Settings and locate the intended domain.
2. Assign an explicit supported PHP version if it currently inherits and PHP-FPM requires an explicit version. Review which other domains share or inherit its configuration.
3. Enable PHP-FPM for the intended domain through the available control. Avoid the server-wide enable action when only one site is under review.
4. Open its PHP-FPM Settings, read the help text and use conservative pool limits appropriate to measured memory and concurrency. Validate settings before updating.
5. Test normal pages, uploads, application login and the previously slow workload. Monitor memory, errors and process saturation after the change.

The domain should use the intended handler without unexpected effects on other sites. Confirm the effective PHP version and application functionality as well as response time.

If the control is unavailable, check inherited versions, runtime support and the active web-server stack. Increasing Max Children without memory planning can worsen an overloaded server. Restore the recorded configuration if the application becomes unstable.

No. Worker management and application efficiency are separate. Use timing and resource evidence to identify whether the bottleneck is PHP concurrency, database work or an external dependency.

• Installing an additional supported PHP version with EasyApache 4
• Reading CPU and concurrent connection fault information
• Moving an addon domain to a new document root
• Adding an EasyApache PHP extension without changing every domain

• cPanel: Multiphp Manager For Whm
• cPanel: Multiphp Manager For Whm User Domain Settings
• cPanel: Multiphp Manager For cPanel