• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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