• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue No Error is displayed in Browser

modit

New Pleskian
Server operating system version
Windows server 2022
Plesk version and microupdate number
18.0.75
Hi i am using Plesk Obsidian 18.0.75 , i am hosting few asp.net applications.


Issue i am facing is that if page has any error the page comes blank in the browser, instead of showing any error message.


Also if i request a page which is not there in the server it shows blank page instead of 404 error page.
 
If you're using ASP.NET Core, the <compilation debug=true will be ignored. You could try to use the following instead.

XML:
  <system.webServer>
    <!-- Force IIS to send detailed errors to the browser -->
    <httpErrors errorMode="Detailed" />

    <!-- Optional: Disable static file error interception -->
    <asp scriptErrorSentToBrowser="true" />
  </system.webServer>

If it still doesn't work you will probably need to configure your program.cs or startup.cs with proper error handling so it shows it.

Ideally you should be looking at the logs anyways or doing logging in remotely for checking the error as it's more secured that way since ASP can leak private info in the errors if it's on a production system.

For the 404, again it depends if you're using ASP.NET Core or not. You could do something like this:

XML:
<configuration>
  <system.web>
    <customErrors mode="On" defaultRedirect="Error.aspx">
    </customErrors>
  </system.web>

  <system.webServer>
    <httpErrors errorMode="DetailedLocalOnly">
      <remove statusCode="404" subStatusCode="-1" />
    </httpErrors>
  </system.webServer>
</configuration>

Now if you are using ASP.NET Core, you'll need to have error handling in your program.cs or startup.cs.
 
Back
Top