• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

application error or service unavaible

D

dsojo

Guest
application error or service unavailable

Hi there

Anyone know what could be happen, randomnly we got service unavailable or application error from sites and must recycle the app pool or in some cases restart the iis domain... we think that the IIS Worker process keeps crashing... our clients are complaining and this is becoming a living hell

Currently we´re hosting about 80 domains plesk 8.2 in a dell 1950 4gb ram 2 x 1.6 quad dore 2xsas 200gb and the server is not heavy loaded and we don´t know what to do...

thanks people and sorry for my bad english i´m trying to do my best.

diego
 
Hi Diego,
First i would advised you to use separate application pool for every domain to avoid their influence on one another. Setting in Plesk: Server -> IIS Application Pool -> Global setting tab, "Always assign one application pool for each domain" radio button.

After that you can deal with particular website which pool is failing and try to find the reason (frequently it occur because of poor writen scripts).

Also look into application and system event logs for errors.
 
i have them all running on different pools, i will see the logs if i found something.

thanks!
 
Back
Top