I'm facing the same issue, and it's been quite a headache. The error originates within the application itself but doesn't always bubble up to the server logs.
To properly diagnose the problem, I recommend enabling full application logging and thoroughly checking all available logs (including framework-specific or custom logs). You may also want to monitor incoming requests and their responses to catch any silent failures or unexpected behavior.