• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Compatibility Issue with WP Toolkit on Plesk for [Domain.tld, redacted]

alexa8

New Pleskian
Server operating system version
Almalinux 9.2
Plesk version and microupdate number
Onyx 18.5.2
Hello Plesk Community,

I hope this message reaches you in good health. I am currently facing a perplexing issue with WP Toolkit on my Plesk-managed website, [redacted], and I'm seeking your expertise to help me troubleshoot and resolve the problem.

Issue Overview: While attempting to perform routine maintenance tasks using WP Toolkit, I encountered an unexpected error. The error message reads: "Error Code 500: Internal Server Error - Unable to complete the requested operation. Please try again later."

Steps Taken:

  1. Verified that both Plesk and WP Toolkit are up to date.
  2. Disabled all plugins to rule out potential conflicts.
  3. Checked server logs, but no specific error related to this issue was found.
The error appears consistently when attempting to update plugins.


Website URL: [redacted]

I would greatly appreciate any assistance or insights from the community to help me diagnose and resolve this unexpected error promptly.

Thank you for your time and expertise.
 
Last edited by a moderator:
Back
Top