• 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 error docs

K

kryz2501

Guest
HI,

We have a customer that relies on custom 404 pages for users to navigate around his website. The pages need to be ASP pages, and read the url that users are typing to redirect them to the correct content.

We have manually changed the IIS configuration to set these to use his 404.asp and 500.asp pages.

HOWEVER

Plesk resets these on a semi regular basis, either when certain tasks are run, (any restore from a plesk backup, or any thing that would cause websrvmng to run on the site and recoinfigure it to plesk defaults).

Now on the *nix version we had vhost.con files to overide the configuration so that custom stuff like this would survive, but what do we do in plesk windows?
 
Back
Top