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

30 websites stopped working due to Appliaction Pool issue by Plesk?

M

MahendraC

Guest
I am hosting reseller from India. Few days back my 30 websites stopped working suddenly. When asked to my ISP who provides me Plesk Control Panel to manage my resellership, my ISP said the sites were stopped by Plesk due to Application pool problem in one or more domains. My Reseller plan is on shared server with this ISP. The sites started working after long time when they said they did reset/recycled application pool of all the sites. They also asked me to enabled application pool setting for all domains, which I did for almost all domains.

I want to know is this possible that all of my sites can be stopped by plesk, if any one domain creates problem due to traffic? Either yes or no, how can I avoid this problem?

What more information you may need to know this issue? Thanks in advance
 
Back
Top