• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. J

    [PPP-17531] WordPress Toolkit Broken on 12.5

    OK thank you for the info!
  2. J

    [PPP-17531] WordPress Toolkit Broken on 12.5

    Yep that instance was in the database table WordpressInstances so I removed it and also removed it's entries from WordpressInstanceProperties. Do you think that's it or might there be data elsewhere to clean up? And how come this happened - perhaps a bug where Plesk can't remove an instance...
  3. J

    [PPP-17531] WordPress Toolkit Broken on 12.5

    Hello, Thanks for the tips. I have run: plesk bin wp_instance --get-list And it does not show the broken instance which is still showing under the Plesk administration UI. So that would indicate that something is 'stuck' but only with the web UI of Plesk? I will check the database next.
  4. J

    [PPP-17531] WordPress Toolkit Broken on 12.5

    Hello, We have CentOS7 and Plesk 12.5. Recently a WordPress installation was hacked so I moved the WordPress directory to public_html-dirty and then restored from backup the files to public_html. I then deleted public_html-dirty and manually updated WordPress via wp-admin. The toolkit is now...
Back
Top