To minimize occurrences of this type, we have implemented a dedicated "pool" in our Windows architecture; this ensures that each application runs in its own exclusive process on the server. This model guarantees that your application will not be affected if another client hosted on the same server has unoptimized code.
Several factors can cause a 503 error (application overload or interruption) on a site hosted on a Windows server, but the issue can be resolved simply by restarting your IIS Application. To do this, follow the steps below:
(STEP 1) First, access your Plesk control panel. E.g., www.yourdomain.com.br:8880
(STEP 2) Click the "Dedicated IIS Application Pool for the Website" icon located at the bottom of the page.
(STEP 2 - NOTE) If you are a Reseller, you will need to access your client`s SUBSCRIPTION/HOSTING account first, and then locate the "Dedicated IIS Application Pool for the Website" icon for that specific subscription/hosting account.
(STEP 3) Click the "Recycle" icon and wait a few seconds. Once the page refreshes, your site will be back online.
(STEP 4) If recycling does not resolve the issue, click "Disable." Wait a few seconds. Then, click "Enable." Wait a few more seconds. If you are using Classic ASP, do not forget to click "Enable 32-bit Applications" and then "OK."
