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

IIS Application Pool for each website

David O.

New Pleskian
Hi,

I have a subscription with 60 websites, but regardless of the quantity, the problem is the same, how or why I can't set a application pool for each domain/subdomain? There are some strong reasons to:

Security. Different app pools running under different accounts.
Isolation. One crashing app won't take down other apps.
Memory. Each app pool will have its own address space.
You may choose to periodically restart one not-so-well behaving app without affecting other applications.

There are also some good reasons to have on application pool for all, but in the end, why can't the admin of server decide it?

Any solution to assign a app pool for each website? Thanks.
 
Back
Top