• 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.

Issue Wordpress Toolkit error message: "Empty instance state"

janpieterk

New Pleskian
Dear people,

Has anyone seen this error before?
User was attempting to update Wordpress plugins, and got the error message "Empty instance state". See below:

Schermafbeelding 2020-12-03 om 16.07.54.png

Apparently, things were in such a bad state at that point that Plesk found it necessary to automatically restore the latest backup of the site in question.

Plesk Obsidian Version 18.0.31 Update #2 on Ubuntu 16.04.7 LTS, WordPress Toolkit version: 5.2.2-4559

Thanks in advance,
Jan Pieter
 
Last edited:
I got it, thank you. Seems like Smart Update was started for this website, but the results of initial checks (gathering the state of your website to compare it with the future state after an update) was missed for some reason. I believe you can safely start an update once again to check if this issue happens by accident, or occurs permanently.
 
Thank you for letting us know! Anyway, we will consider improvements in reporting an actionable and clear error in such case.
 
Back
Top