• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved WordPress Toolkit: PHP on v7.3.22 still get unable to update error

rbrady5

New Pleskian
I have multiple websites running on PHP v7.3.22 for which WP Toolkit gives the following error when attempting an update on plugins, themes, and core. The lowest version of PHP enabled on the server is v7.1.33. The issue has recently started occurring within last few weeks. I have not been able to resolve it. I have tried updating a few sites to PHP v7.4.10 but no luck. I can log into WordPress on sites and run updates without error.

Server is running Plesk Obsidian Version 18.0.29 Update #3, last updated on Sept 1, 2020 06:28 AM on Ubuntu 16.04.7 LTS.

Error says: "Unable to update WordPress because WordPress version 5.5.1 requires PHP version 5.6.20 or newer. Change PHP settings on the target domain to use a newer PHP version and run the update again."
 
Back
Top