How to Resolve 503 Service Unavailable Errors and Manage Dedicated IIS Application Pool in Plesk

"HTTP Error 503. The service is unavailable." on a Windows-hosted website almost always means IIS has no running worker process for your site: the application pool has stopped, usually because your application crashed repeatedly, or the site has been taken offline on purpose. This guide shows how to tell which one it is, what you can fix yourself in Plesk, and when to ask Domain India support.

1. What a 503 on IIS means

A 503 comes from the web server, not from your code. IIS is up and answering, but it can't hand your request to the process that runs your site. On Windows hosting that is nearly always one of these:

A 503 is different from a 500. A 500 means your application ran and failed on that request; a 503 means it isn't running at all.

2. Rule out app_offline.htm first

ASP.NET takes an application offline whenever a file named app_offline.htm sits in its root folder. Deploy tools create it, and a failed or interrupted upload can leave it behind.

3. Why an application pool stops

IIS has a safety feature called rapid-fail protection. If the worker process for a pool crashes too many times in a short period (by default 5 times in 5 minutes), IIS stops the pool rather than restart it forever. From then on, every request gets a 503.

What makes a .NET worker process crash:

• an unhandled exception during startup, such as a missing configuration value, a bad connection string or a database that can't be reached;
• a stack overflow or an infinite recursion in your code;
• a DLL built for a .NET version the server doesn't have, or a 32/64-bit mismatch;
• running out of memory under a leak.

Memory or CPU limits set on the pool can also make IIS recycle or stop it. The fix is in your application: the pool will keep stopping until the crash is gone.

4. Find the crash in your logs

Before restarting anything, find out why it stopped.

• Plesk logs. Open your domain in Websites & Domains and choose Logs. Look at the entries from just before the 503 started. See checking Plesk logs.
• ASP.NET Core startup log. In web.config, set stdoutLogEnabled="true" on the aspNetCore element, create an empty logs folder inside httpdocs, restart the app and read the newest file in logs. Set it back to false when you're done.
• Your own application log, if your app writes one.

The Windows Event Log, where IIS records pool shutdowns, is on the server and isn't available to shared hosting customers. If your own logs show nothing, ask support to look there for you.

5. Restart the application pool

Once you have fixed the cause, or if you need the site back while you investigate:

If your Plesk has pool controls (a dedicated application pool): open your domain, go to Dedicated IIS Application Pool and click Start if it is stopped, or Recycle if it is running. The step-by-step version is in restarting your app pool in Plesk.

If it doesn't: your subscription uses a shared pool. Ask support to start or recycle it, using live chat or a ticket. Tell us your domain, the time the 503 started and what you changed just before.

6. The dedicated IIS application pool

A dedicated application pool runs your subscription's sites in their own worker process, separate from other customers. That brings two benefits for 503 problems:

• another subscription's crash or traffic can't stop your site;
• you can see your pool's state and start or recycle it yourself.

Whether a subscription gets a dedicated pool is set by its hosting plan, so it isn't a switch you turn on in Hosting Settings. Among the Domain India Windows plans, ASP Enterprise lists a dedicated app pool. If you are on another plan and keep needing pool restarts, consider upgrading.

7. Check your .NET and site settings

Wrong settings make an app crash on its first request, so they show up as a 503 soon after a change.

• .NET version. In your domain's ASP.NET or hosting settings in Plesk, make sure the selected version matches the one your app targets. ASP.NET Core apps need a pool with No Managed Code; .NET Framework 4.x apps need CLR v4.0.
• web.config. If you edited it just before the 503, restore the previous copy.
• Default document. If the home page gives a 403 or 404 instead, check that default.aspx, index.html or your chosen start page exists.

More about these settings is in the IIS application pools guide.

8. Preventing repeat 503s

Ready to stop chasing 503s? Compare the Windows hosting plans, or open a support ticket if your pool keeps stopping. Support is on 24/7 live chat, and tickets get a first response within 15 minutes.