better error reporting on broken websites, using Windows 2008 & DotNetPanel?

[SoftDux]

Hi, Is there any way to get better error reporting on broken websites, for the end users? For example, we got a support ticket from a furious user, cause "we denied access to her website". She got a "404 Access Denied" error message on her website. That's it, nothing more, nothing less.
Puzzled, I looked at her website on the server directly using Firefox when I got a more indicative error message as follows:

Most likely causes: •A default document is not configured for the requested URL, and directory browsing is not enabled on the server

I then logged into her account as noticed that her default document was Default.html, but she didn't have "Default.html" listed as a default document. So I added it, and the website was fixed. How do I display these errors to end users?

The server runs Windows 2008 + IIS7 + DotNetPal 2.8.14

[Louisvdw]

I think the only way is to educate the users.

[SoftDux]

Originally Posted by Louisvdw

I think the only way is to educate the users.

on what?

[Louisvdw]

On what default page they should use.

[SoftDux]

Originally Posted by Louisvdw

On what default page they should use.

Yes, true in this regard the clients needs some training. But that's nearly impossible in the hosting industry.

The bigger problem is that IIS, or maybe even DNP doesn't produce decent errors like Apache does. And I would like to know how to enable more error reporting for clients in this regard