• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Wordpress Tool broken in Plesk 12.5.30

southy

Basic Pleskian
Hi,

I have experienced a number of problems with the wordpress toolkit since the update onto 12.5.30.
To check if some bogus old config might be the reason, I set up a completely fresh machine not longer than 30 minutes ago, with no configuration changes whatsoever: CentOS 7 / Plesk 12.5.30

Whenever I install (fresh, from Plesk repository) a wordpress, this very helpful error is displayed:
U4iyA.jpg


Performing the security check (selecting every option) takes only about 1sec - and does nothing: if you re-check, everything is unchanged.

panel.log reads:
[2015-12-13 18:56:10] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/wpmng' '--user=mila' '--php=/usr/bin/php' '--' '--path=/var/www/vhosts/XXX.de/httpdocs' 'core' 'info' '--format=json' '--check-updates=true'] with exit code [255]
[2015-12-13 18:56:10] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/wpmng' '--user=mila' '--php=/usr/bin/php' '--' '--path=/var/www/vhosts/XXX.de/httpdocs' 'init' 'secure' '--checkers=adminUsername,dbPrefix,secureConfig,secureIndexing,securityKeys,versionInfo,securityPermissions' '--format=json'] with exit code [255]
[2015-12-13 18:56:10] ERR [1] '/usr/local/psa/admin/bin/wpmng' '--user=mila' '--php=/usr/bin/php' '--' '--path=/var/www/vhosts/XXX.de/httpdocs' 'init' 'secure' '--checkers=adminUsername,dbPrefix,secureConfig,secureIndexing,securityKeys,versionInfo,securityPermissions' '--format=json' failed with code 255.

Seems to be a bug. Please fix.

Note: Yes, I _do_ know this bug here. But as I said: I just freshly installed the machine and the wordpress out of the Plesk repository: there has nothing been modified, I haven't even logged in WP at all. So it can not be related to a plugin... except you deliver broken stuff in the first place.

Best regards,
southy
 
I glad to inform you that the issue is fixed in recently published Plesk updates: Plesk 12.5.30 MU#15 & Plesk 12.0.18 MU#72
Please check KB article for details: https://kb.odin.com/en/127725
  1. Install latest Plesk microupdate.
  2. To restore integration with affected instances do the following:
    Go to Home > Wordpress and click "Check for updates".
 
I glad to inform you that the issue is fixed in recently published Plesk updates: Plesk 12.5.30 MU#15 & Plesk 12.0.18 MU#72
Please check KB article for details: https://kb.odin.com/en/127725
  1. Install latest Plesk microupdate.
  2. To restore integration with affected instances do the following:
    Go to Home > Wordpress and click "Check for updates".

Thanks That worked like a charm!
 
I glad to inform you that the issue is fixed in recently published Plesk updates: Plesk 12.5.30 MU#15 & Plesk 12.0.18 MU#72
Please check KB article for details: https://kb.odin.com/en/127725
  1. Install latest Plesk microupdate.
  2. To restore integration with affected instances do the following:
    Go to Home > Wordpress and click "Check for updates".
This didn't work for me.

I still see the following error when do a "Check for updates".

Code:
[2015-12-16 22:12:33] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/wpmng' '--user=fenfnl' '--php=/opt/plesk/php/5.6/bin/php' '--' '--path=/var/www/vhosts/fris-en-fruitig.nl/httpdocs' 'core' 'info' '--format=json' '--check-updates=true'] with exit code [255]

I have the following Plesk running:

Plesk version 12.5.30 Update #15, last updated at Dec 16, 2015 10:11 PM
 
Back
Top