This is a quick reference for the errors Domain India Windows (Plesk) hosting customers meet most often: website errors from IIS, Plesk panel sign-in problems, email and database errors. Each row gives the usual cause and the first fix to try. For anything the table doesn't settle, the answer is in your logs.
Most website errors on Windows hosting come from four places: a broken or locked web.config (500.19), an app that crashes at startup (500.30, 503), a stopped application pool (503) or a missing default document (403). Find the exact error in your Plesk logs before changing anything. For the Plesk panel, sign in with the Plesk button in the client area and use port 8443 only. For email, send on port 465; port 587 is not open on Windows hosting.
The error text a visitor sees is only a summary. The full guide to finding and reading logs is how to check Plesk logs for troubleshooting.
1. Website errors (IIS)
| Error | Usual cause | First fix |
|---|---|---|
| 403 Forbidden | No default document in the folder, and directory listing is off | Upload default.aspx or index.html, or add your start page to the default documents |
| 404 Not Found | Wrong URL, file not uploaded, or a rewrite rule | Check the file is in httpdocs with the exact name; review rewrite rules in web.config |
| 404.7 | IIS blocks that file extension | Rename the file, or serve it through your app |
| 500 Internal Server Error | An exception in your code | Turn on detailed errors briefly and read the message |
| 500.19 | web.config is invalid or changes a locked setting | Restore the last working web.config; remove the section you added |
| 500.30 | ASP.NET Core app failed while starting | Turn on the stdout log in web.config and read it |
| 500.31 / 500.32 | .NET runtime missing, or 32/64-bit mismatch | Retarget to an installed version, or publish self-contained |
| 503 Service Unavailable | App pool stopped after repeated crashes, or app_offline.htm present | Delete app_offline.htm; find the crash; see the 503 guide |
For 503 in detail, see resolving 503 errors on IIS. For deployment problems, see deploying an ASP.NET application in Plesk.
2. Turning on detailed errors, briefly
In web.config, inside system.web, for .NET Framework sites:
<customErrors mode="Off" />For ASP.NET Core, set stdoutLogEnabled="true" on the aspNetCore element and create an empty logs folder in httpdocs. Both expose internals to visitors, so switch them off as soon as you have the message.
3. Plesk panel errors
| Problem | Usual cause | First fix |
|---|---|---|
| Plesk page doesn't load | Wrong port, or your network blocks 8443 | Use the Plesk button in the client area; test on mobile data |
| Login failed | Wrong or old password | Use the one-click Plesk button in the client area instead of typing a password |
| Works on mobile data but not on your usual network | Your network, or a block on your IP address | Ask support, and include your public IP address |
| "Limit reached" when adding something | Your plan's limit on websites, mailboxes or databases | Remove unused items or upgrade the plan |
See how to log in to Plesk for every sign-in method.
4. Email errors
- Can't send from an email app: use SMTP on port 465 with SSL/TLS and authentication on. Port 587 is not open on Windows hosting. All ports are in Domain India port numbers.
- Authentication failed: the username is the full email address; reset the mailbox password in Plesk if you're unsure.
- Mailbox full: delete old mail or raise the mailbox size in Plesk, within your plan's disk.
- Mail not arriving: check your domain's MX record points at the hosting, and that SPF is set. If it still fails, ask support to check the mail logs, which customers can't see.
5. Database errors
- Can't connect: use the database server name exactly as Plesk shows it, not always
localhost, and connect from your site on the server. See what to use for an MSSQL connection string. - Login failed for user: the database user or password in your connection string doesn't match Plesk. Reset the database user's password in Plesk and update the string.
What causes HTTP Error 500.19 on Windows hosting?
Your web.config is invalid XML or tries to change a setting that is locked on the shared server. Restore the last working copy of web.config, or remove the section you added most recently.
Why does my site give 403 Forbidden on Windows hosting?
Usually there is no default document, such as default.aspx or index.html, in the folder, and directory listing is off. Upload a start page or add yours to the default documents list in Plesk.
How do I fix 503 Service Unavailable in Plesk?
Delete any app_offline.htm in httpdocs, then find why the application crashed using the Plesk logs. Once fixed, start or recycle the application pool, or ask support to if your plan has no pool controls.
Which SMTP port should I use on Windows hosting?
Use port 465 with SSL/TLS. Port 587 is not open on Domain India Windows hosting.
I can't log in to Plesk. What should I try first?
Use the one-click Plesk button on your hosting service in the Domain India client area. If the page doesn't load at all, try another network, because some office networks block port 8443.
Still stuck after the table? Open a support ticket with your domain, the exact error and when it started. Support is on 24/7 live chat, and tickets get a first response within 15 minutes.
Send us your domain, the exact error text and the time it happened, and we'll help you fix it.
Open a ticket