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

Question Is there a way to expand on a 500 error?

PDXMember

New Pleskian
I am attempting to troubleshoot a script import for Joomla to import from Wordpress to Joomla.

When doing this, I am getting a 500 error in the logs, but it is only descriptive enough to indicate the script name. Is there a way to expand this some more so I can see what the cause of the 500 error is?

NOTE: Joomla and Wordpress themselves are installed and working properly.
 
No, the only way is to look into the error_log. However, I have never seen a 500 error in there that did not state the reason why it happened, too.
 
Back
Top