Skip to main content

Recurring HTTP 500 Errors Resolved Only by a Full Reboot

Symptom​

The Netwrix Endpoint Protector Server periodically returns HTTP 500 errors across the console. A full server reboot temporarily clears the errors, but they recur every few days.

Cause​

This pattern typically indicates the server is undersized for its current load — database size, log volume, or number of managed endpoints — rather than a one-time import or configuration failure. A reboot only clears the symptom by resetting exhausted resources or hung processes; it does not resolve the underlying sizing issue, which is why the errors return.

In rare cases, this behavior can occur after a server migration to the current image-based platform, if load increases without a matching resource review. It can also occur on a longstanding server whose load has grown beyond its original sizing.

Resolution​

  1. Verify the CPU, RAM, and disk allocated to the server against the current Server Requirements. An undersized appliance is the most common root cause of both general UI slowness and recurring server errors.
  2. If resources are below the recommended minimums, increase them before continuing.
  3. If resources already meet or exceed the minimums and the errors persist, raise a Netwrix Support ticket to request a review and adjustment of the server's PHP configuration.
tip

If you are troubleshooting general console slowness rather than specific HTTP 500 errors, see User Interface Performance Issues for the full set of possible causes.