• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Unable to read or execute files from the WordPress root directory

ToddE

New Pleskian
After migrating a site to a new server and scanning for WordPress installations: I receive the following:

{"err_code":40001,"err_message":"Unable to read or execute files from WordPress root directory: D:\\PLESK\\VHOSTS\\pointmonitor.com\\httpdocs\/"} {"err_code":40003,"err_message":"Unable to read or execute files from wp-admin\/includes directory': D:\\PLESK\\VHOSTS\\pointmonitor.com\\httpdocs\/wp-admin\/includes"} {"err_code":40004,"err_message":"Unable to read or execute files from wp-includes directory: D:\\PLESK\\VHOSTS\\pointmonitor.com\\httpdocs\/wp-includes"} {"err_code":40005,"err_message":"Unable to read or execute files from wp-content directory: D:\\PLESK\\VHOSTS\\pointmonitor.com\\httpdocs\/wp-content"}

I cannot figure out what permissions it wants. Private server, so I do have access to IIS 7. I have run the Plesk Reconfigurator > Correct disk permissions: no joy.
 
Database structure is the same for Windows and Linux Plesk versions.
 
The KB article has been updated with a link to a patch for this issue:

https://kb.odin.com/en/127725

I can confirm it fixes the problem on Plesk 12.5 for Windows and Wordpress 4.4. I applied the patch and then had to run a "Resynchronize" operation on each of the affected WP sites.
 
Back
Top