I have a small cloud server PLESK and am trying to meet PCI Compliance. Got it down to a handful of errors from Qualays. I can’t seem to understand how to solve the last few errors. How would I fix this? Do I just need to create a custom error page?

THREAT: This finding will be reported when run time errors, verbose server errors, and potential stack trace are detected

The following are two examples of 150022

• WAS will send payload without URL encoding and cause an error. Note most browsers now URL encode these payloads, in order to reproduce the issue curl or a proxy
  can help bypass the automatic URL encoding.
• Errors can also be caused due to the speed of the scanner sending payloads. The report provides the payload that caused the error if this is consistently reported with
  SQL payloads it is worth taking an extra look.

IMPACT:
Verbose error messages often expose technical details that are helpful to attackers. Verbose errors can allow attackers to learn “inside” information about the application
and/or hosting infrastructure, allowing them to target it more effectively.

SOLUTION:
Implement strong error and exception handling to ensure that the web application displays only generic error messages. Avoid returning stack traces, debugging
information, or other technical details to the client side. The application should also implement rigorous input data validation. Restrict user-supplied data to consist of a
minimal set of characters necessary for the input field and validate the data to ensure it conforms to the expected format.

RESULT:
url: urlhidden.php?prod=file%3A%2F%2F%2Fetc%2Fpasswd
Tested parameter: prod
Payload: file:///etc/passwd
variants: 44
comment: Response status: 200