Installing cpAddon Wordpress Error MultiPHP Disabled

[Kurieuo]

When installing Wordpress via the Wordpress Manager/Site Software in cPanel, an error is output as follows:

Error: The system could not run the “/usr/local/cpanel/cpaddons/cPanel/Blogs/WordPressX/wordpress_use_best_php” install script and received the error code “255”: Cpanel::Exception/(XID cjvbwa) Your hosting provider must enable the “MultiPHP Manager” feature to perform this action. at /usr/local/cpanel/Cpanel/AdminBin/Call.pm line 96. Cpanel::AdminBin::Call::_parse_cpwrapd_response(HASH(0x12ac1d0)) called at /usr/local/cpanel/Cpanel/AdminBin/Call.pm line 50 Cpanel::AdminBin::Call::call("Cpanel", "multilang", "UPDATE_VHOST_CPANEL", "ea-php72", "domain.com") called at /usr/local/cpanel/Cpanel/API/LangPHP.pm line 136 Cpanel::API::LangPHP::php_set_vhost_versions(Cpanel::Args=HASH(0x2358460), Cpanel::Result=HASH(0x2784968)) called at /usr/local/cpanel/cpaddons/cPanel/Blogs/WordPressX/wordpress_use_best_php line 129 scripts::wordpress_use_best_php::run("scripts::wordpress_use_best_php", "--domain", "domain.com") called at /usr/local/cpanel/cpaddons/cPanel/Blogs/WordPressX/wordpress_use_best_php line 27​

Now I've been using CloudLinux's PHP Selector for some time. I disabled MultiPHP to save confusion for users, and chose to go with PHP Selector as I read that it was more seucre, and could even be imported into cPanel and replace MultiPHP altogether (perhaps just a rumour?).

In any case, it seems the Wordpress installer expects MultiPHP and doesn't consider a CloudLinux implementation without the MultiPHP enabled. Yet, Wordpress still looks to install correctly. It's just its selecting the best PHP version that stuffs up.

Is this a bug, can it be easily fixed?

As a second to that, Wordpress is really the only cPAddon. Is it just going to be gotten rid of? If that is the case, thinking maybe I should just disable it altogether and consider other addon software solutions if such auto-installing functions are desired.

 

[cPanelLauren]

Hi @Kurieuo


This is the second time I've heard this occurring with PHP selector today, out of curiosity do you have the following php extensions installed on the php version you're using for the WordPress site?

dom
gmagick
SimpleXML
ssh2
xml
xmlreader
curl
date
exif
filter
ftp
gd
hash
iconv
imagick
json
libxml
mbstring
mysqli
openssl
pcre
posix
sockets
SPL
tokenizer
zlib

 

[Kurieuo]

All required WP extensions were selected under PHP 7.2 and then some for the cPanel account. However, the actual cpAddon install script is run at command isn't it? Would PHP Selector PHP versions and extensions affect a shell executed install script?

 

[cPanelLauren]

It should function with altPHP without issue. Do you have the MultiPHP selector UI available in cPanel for the user?

 

[Kurieuo]

Thanks Lauren.

No, the MultiPHP is disabled, as far as I'm aware. It was enabled initially, but I disabled it to save user confusion. That was 2 years ago, perhaps my disabling was simply superficial. I can't see in WHM where it specificially says enable/disable?

Maybe it is enabled and I just thought I disabled it. System default is PHP 5.6 (ea-php56) -- which I've been meaning to upgrade once I ensure websites are all changed from native to altPHP 5.6+ via CageFS.

Accounts in questions have CageFS enabled and were set to altPHP 7.2. One was still set to native version (ea-php56).

 

[Kurieuo]

I just setup a test account.

Ensured that alt-PHP72 was selected via MultiPHP Manager (in WHM) for the new account.

Trying to install Wordpress still gave:

Error: The system could not run the “/usr/local/cpanel/cpaddons/cPanel/Blogs/WordPressX/wordpress_use_best_php” install script and received the error code “255”: Cpanel::Exception/(XID 4hpaar) Your hosting provider must enable the “MultiPHP Manager” feature to perform this action. at /usr/local/cpanel/Cpanel/AdminBin/Call.pm line 96. Cpanel::AdminBin::Call::_parse_cpwrapd_response(HASH(0x231a190)) called at /usr/local/cpanel/Cpanel/AdminBin/Call.pm line 50 Cpanel::AdminBin::Call::call("Cpanel", "multilang", "UPDATE_VHOST_CPANEL", "ea-php72", "php.domain.com") called at /usr/local/cpanel/Cpanel/API/LangPHP.pm line 136 Cpanel::API::LangPHP::php_set_vhost_versions(Cpanel::Args=HASH(0x37f3068), Cpanel::Result=HASH(0x22ff328)) called at /usr/local/cpanel/cpaddons/cPanel/Blogs/WordPressX/wordpress_use_best_php line 129 scripts::wordpress_use_best_php::run("scripts::wordpress_use_best_php", "--domain", "php.domain.com") called at /usr/local/cpanel/cpaddons/cPanel/Blogs/WordPressX/wordpress_use_best_php line 27​

I'm assuming the fact I can use MultiPHP Manager (in WHM) that it is enabled alongside CloudLinux's PHP Selector, and that I've only allowed users to see the PHP Selector and not MultiPHP (via features) to switch their PHP version.

 

[cPanelLauren]

MultiPHP needs to be enabled in cPanel for this to work, it's also noted in the error:

(XID 4hpaar) Your hosting provider must enable the “MultiPHP Manager” feature to perform this action.

You can enable MultiPHP Manager for cPanel users by editing the featurelist for the package assigned to the account at WHM>>Packages>>Feature Manager

 

[Kurieuo]

Well yes, I've said MultiPHP is disabled in the topic title --

Now I've been using CloudLinux's PHP Selector for some time. I disabled MultiPHP to save confusion for users, and chose to go with PHP Selector as I read that it was more seucre, and could even be imported into cPanel and replace MultiPHP altogether (perhaps just a rumour?).

In any case, it seems the Wordpress installer expects MultiPHP and doesn't consider a CloudLinux implementation without the MultiPHP enabled. Yet, Wordpress still looks to install correctly. It's just its selecting the best PHP version that stuffs up.​

Lots of cPanel server ops just go with CloudLinux's PHP Selector. When I did my research, it was generally the one opted for a couple years back. Since either MultiPHP or CL PHP Selector can be used (and cPanel supports CL as well) -- such shouldn't really bug out like it does.

 

[cPanelLauren]

This error is specifically related to it being disabled though, the word press manager does expect multiPHP manager to be enabled, while we do recognize and support CloudLinux it is still a 3rd party software.

 

[planetjoin]

This error is specifically related to it being disabled though, the word press manager does expect multiPHP manager to be enabled, while we do recognize and support CloudLinux it is still a 3rd party software.

Sorry for bring this post alive again.. But then, the only way to use wordpress manger and avoid the BIG red warning error, is to enable the cpanel native multi-php selector?

For all people using cloudlinux is not good to enable it to avois any confusion on the clients side with 2 different php selectors.

I ask, is not any way to avois that check in the wordpress manager installing ? I mean, install WP without check the multiphp selector?

Thanks
Fabian

 

[bennhana]

I have been reading this post but it's not helping me get a solution to my problem. I know maybe someone already asked this question but I desperately need help.

 

[cPanelLauren]

THere is an open case on this CPANEL-28040 as well as CPANEL-27388 which are both in the monitored state and not resolved. In the case's comments it looks like they're having issues reproducing this behavior. I'd suggest opening a ticket so that we can investigate further.