• 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.

Get detailed error reports...

G

ghawley

Guest
I have looked all over the internet and tried several things to get detailed error reports for ASP scripts instead of the default Internal Server Error reports that result from errors in asp scripts. Can someone tell me how to get detailed error pages that tell you what the error is?

I see in IIS that errors are being directed to the default error pages but I'm not sure how to create the detailed error pages to direct it to.

Any help would be fantastic. Thanks.
 
If i remeber it correctly, this is a setting in the internet explorer. You have to activate 'show detailed errors' or something like this in the settings of IE in the 'Advanced' Tab.
 
This is not end user related issue.

ghawley: goto Plesk CP -> Domains -> domain.com -> Setup -> un-check "Custom Error Documents"
 
You must log in or register to reply here.

Similar threads

Azurel
Not used PHP versions removed, but Plesk reports missing versions
Replies
4
Views
4K
Azurel
Azurel
K
Resolved Send detailed error to client-side for 500 errors with ASP.NET
Replies
1
Views
12K
kelmore5
K
Hangover2
Critical security issue fixed on 24–25 February 2026 (Plesk Obsidian 18.0.75 Update 1 / 18.0.76 Update 2) — request for vulnerability details
Replies
4
Views
10K
Hangover2
Hangover2
M
Issue PHP Cronjob in Plesk -- Lack of documentation. Lack of structure. Multiple Issues.
Replies
4
Views
4K
MHC_1
M
brother4
Issue plesk repair fs fails with custom DKIM selector: expected file but found symlink
Replies
3
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top