• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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