• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Server Error 500 Internal Server Error for one of my websites

cientiros

New Pleskian
Anyone have any troubleshooting suggestions for this:

Server Error​

500​

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator to inform of the time the error occurred and of anything you might have done that may have caused the error. More information about this error may be available in the server error log.


Here's the log 500 error:
2021-03-21 07:54:12Error72.197.96.117500GET / HTTP/1.0
https://52.33.213.19/smb/web/view
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:86.0) Gecko/20100101 Firefox/86.0
3.32 KApache SSL/TLS access
 

Attachments

  • VetFunder 500 error.JPG
    VetFunder 500 error.JPG
    202.6 KB · Views: 56
In the combination that your log exposes, it is very likely that an include in a page refers to a resource that is missing from the server. Instead, a custom "not found" item is being loaded which includes a resource that is missing from the server. This again triggers a "not found" ... For that reason the page body gets bigger and bigger. This eventually leads to the excessive page body size that cannot be processed by the server.

The scenario can be a little different, but in the end it is normally infinite rewrites and includes that are causing this specific issue. It could be the "not found" loop or another type of loop, e.g. in some content management plugin where one messages is nested in another etc. It is not possible to identify the exact cause from the log entries.
 
In the combination that your log exposes, it is very likely that an include in a page refers to a resource that is missing from the server. Instead, a custom "not found" item is being loaded which includes a resource that is missing from the server. This again triggers a "not found" ... For that reason the page body gets bigger and bigger. This eventually leads to the excessive page body size that cannot be processed by the server.

The scenario can be a little different, but in the end it is normally infinite rewrites and includes that are causing this specific issue. It could be the "not found" loop or another type of loop, e.g. in some content management plugin where one messages is nested in another etc. It is not possible to identify the exact cause from the log entries.
Ok.

@IgorG addressed this and his solution worked for me.
Do you see this Apache and nginx setting in Additional Apache Directives to not be the solution?

<IfModule mod_security2.c>
SecResponseBodyLimit 546870912
</IfModule>



 
Rule no. 1: When IgorG posts something, it is most always the best possible choice for you to follow his recommendation. He knows Plesk excellently and he is a brillant Linux wizard, too. It is very unlikely that something that comes from him won't work.

But: Sure you can expand the limit for the amount of data that is allowed. It seems to "solve" your issue. But there is a reason for limits. Normally, crossing such a limit means that something else is wrong with a content. I'd rather tackle the underlying issue than avoiding error messages by expanding a threshold to avoid a symptom.
 
Back
Top