How can I see the details of the ASP 500 Internal Server Error?

You need to go to the 'Error Pages' section in IIS and activate the 'Detailed errors' option from 'Edit Feature Settings', or add httpErrors settings to the web.config file.

How to make a custom error page with web.config file?

By adding definitions like inside the tag in your web.config file, you can manage custom error pages.

Do your Windows Hosting packages support ASP?

Yes, Eka Sunucu Windows Hosting packages fully support Classic ASP and the latest ASP.NET Core versions.

How to Enable ASP Error Pages? | Windows Server Config 2026 - Eka Sunucu | Turkey's Leading Digital Services Automation Provider

Manage ASP Error Pages

Here is all the information you need to activate special error pages for your ASP and ASP.NET projects on Windows servers, see the details of general errors such as 500 Internal Server Error, and create SEO-compatible 404 pages. Secure and high-performance configuration guide in accordance with 2026 year standards.

Why Are ASP Error Pages Important?

Error management is not only a technical necessity, but also the cornerstone of user experience and search engine optimization (SEO).

By default, Windows servers (IIS) hide detailed error messages for security reasons when an error occurs and show the user a generic "500 - Internal Server Error" or "An error occurred on the server" message to the user. This is safe for a live website, but prevents you from finding the source of the error in development.

2026 Highlights According to Web Standards:

Security (Security Through Obscurity): You should only show error details to your own IP address (Localhost) and close it to the outside world.
User Experience (UX): Instead of "Server Error", you should present guiding "404 Page Not Found" or "We Are Under Maintenance" pages that are appropriate to the design of your site to your users.
SEO (E-E-A-T): Google perceives special error pages that return correct HTTP status codes (Status Codes) and keep the user on the site as an authority signal.

Method 1: Configuration with Web.Config

The most practical and common method is to edit the web.config file in the root directory of your application.

Opening ASP.NET Errors (CustomErrors)

To manage ASP.NET based errors or view details <system.web> block is used. This method is valid for old type ASP.NET errors.

web.config

<configuration>
    <system.web>
        <!-- mode="Off" to show errors to everyone -->
        <!-- To view on the server only mode="RemoteOnly" (Recommended) -->
        <customErrors mode="Off" />
    </system.web>
</configuration>
                        

Managing IIS Error Pages (httpErrors)

To manage all errors in IIS 7.0 and above (Windows Server 2019, 2022, 2025), including static files and Classic ASP <system.webServer> under httpErrors is used. This is the most comprehensive method.

web.config

<configuration>
    <system.webServer>
        <!-- errorMode="Detailed" : Shows detailed error to everyone (For development environment) -->
        <!-- errorMode="DetailedLocalOnly" : Shows detailed error only to the server, general error to the outside -->
        <httpErrors errorMode="Detailed" existingResponse="PassThrough" />
    </system.webServer>
</configuration>
                        

Warning: In a live (Production) environment errorMode="Detailed" Leaving it may create a security vulnerability. Error codes may reveal database schema or file paths.

Custom Error Page Redirect (404, 500)

Show your own designed pages instead of standard IIS errors to provide your users with a professional experience. This process is important to avoid the "Soft 404" error in 2026 SEO standards.

web.config

<configuration>
    <system.webServer>
        <httpErrors errorMode="Custom" existingResponse="Replace">
            <remove statusCode="404" />
            <error statusCode="404" path="/hatalar/404.asp" responseMode="ExecuteURL" />

            <remove statusCode="500" />
            <error statusCode="500" path="/hatalar/500.asp" responseMode="ExecuteURL" />
        </httpErrors>
    </system.webServer>
</configuration>
                        

Method 2: Setting via Plesk Panel / IIS

You can also make these settings through the hosting control panel without writing code.

Login to Plesk Panel: Access your hosting management panel.
Virtual Directories: Find the "Error Pages" icon in the management area of the relevant domain.
Feature Settings: Click "Edit Feature Settings" in the right menu or settings tab.
Detailed Errors: In the window that opens, select the "Detailed errors" option and save it.

This process is done automatically on the server side. web.config It will update your file.

2026 SEO Trends and Error Pages

Error management has become even more important after Google's "Helpful Content" and "Core Web Vitals" updates.

Crawl Budget

Pages that do not return the correct 404 response (Soft 404) waste search engine bots' time and eat into your site's crawl budget.

User Trust

A specially designed 404 page containing an in-site search bar or popular links prevents the user from bouncing off the site (Bounce Rate).

Technical Health

Pages that constantly give 500 errors reduce the technical health score of your site and cause ranking loss. Tracking and fixing errors is a must.

Our Windows Hosting Packages

High-performance, NVMe SSD disk and %100 compatible infrastructure for your ASP and ASP.NET projects.

Windows Startup	1 Website	Unlimited Traffic	Plesk Panel	89,90 ₺ / Ay	Review
Windows Professional	5 Website	Unlimited Traffic	NVMe SSD	149,90 ₺ / Ay	Review
Windows Enterprise	Unlimited Sites	Private IP Address	Premium Support	299,90 ₺ / Ay	Review

For more options our economic packages you can review.

Frequently Asked Questions

I am getting "An error occurred on the server" error in my Classic ASP files, what should I do?

This is a general IIS error. To see the line number and cause of the error, you must set the "Send Errors To Browser" option to "True" in the IIS -> ASP -> Debugging Properties section. You can find this option under "IIS Settings" in the Plesk panel.

I edited the web.config file, but the site gives 500 error, why?

The web.config file is in XML format and at the slightest syntax error (unclosed tag, wrong quotation mark, etc.) your site will stop working with the 500.19 error. Before editing the file, make sure to back it up and perform XML validation.

Can I switch to Windows without changing my hosting package?

If you are currently using Linux hosting, you need to change packages and move your data to switch to Windows hosting. Eka Sunucu technical team contact We can provide you with free transportation support in this regard through our channels.

Custom Server Services

Standard Servers

Custom Server Services

Standard Servers

Contact Us

Manage ASP Error Pages

Why Are ASP Error Pages Important?

Method 1: Configuration with Web.Config

Opening ASP.NET Errors (CustomErrors)

Managing IIS Error Pages (httpErrors)

Custom Error Page Redirect (404, 500)

Method 2: Setting via Plesk Panel / IIS

2026 SEO Trends and Error Pages

Crawl Budget

User Trust

Technical Health

Our Windows Hosting Packages

Frequently Asked Questions

Call now to get more detailed information about our products and services.