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

Custom Errors - be able to add your own

Colin_Slater

New Pleskian
Hi,

Currently, there are only a few standard custom errors that can be setup in PLESK 12 on the hosting system I'm using.
I would like to be able to trap 500.100 errors, which are ASP errors generated from scripts. My custom error page traps this information into a database, and logs various information, like the user that was logged into the database application, their browser etc... all information which is really useful in debugging problems.

Currently, I can only set error 500 up, which doesn't quite do the same thing.

Is it possible to have this as a new feature in PLESK - the ability to add custom error pages to the already available list.
 
Hi Colin_Slater,

We are working on custom errors redesign for next Plesk releases: it will be possible to set an error page for any of 40x/50x http codes.
No ETA for now, we will announce public preview as soon as it will be available.
 
Back
Top