• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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