Asp-Net CustomErrors Mode Off Error When Trying to access Working Webpage

How to Disable ASP.NET Custom Errors in Web.config

You have created an asp.net webpage and have uploaded it onto a webserver. However when you try to view the page remotely, you got errors about the customerror tag in the web.config file. 

The page works locally with no errors or warnings. Also if you upload the page as a .html file, I can view it fine remotely. I have seen a lot of other people with this error, but the 'solutions' just say to change the customErrors tag to 'Off', which you have done and does not work, do you know is there an issue with the webserver or what could be the problem here? 

Many times during the processing of an ASP.NET application, you will get the following default runtime error

Server Error in '/' Application.

---

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File --> <configuration>     <system.web>         <customErrors mode="Off"/>     </system.web> </configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File --> <configuration>     <system.web>         <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>     </system.web>  </configuration>

Solution:

This is a generic error generated by ASP.NET When customErrors are set to ON. To resolve this issue, create a web.config

Change From

<customErrors mode="On"/>

To

<customErrors mode="Off"/>

Details Written as Below

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>