• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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