Causes NGINX Helper to 502 when purging cache

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    A 502 error is a generic one from Nginx, you need to find out the underlying PHP error that causes it or precedes it. The errors reported by that thread suggest that the cache purging is triggering a large number of PHP errors, and when QM tries to report these errors in the response header it exceeds the default Nginx header size limit of 4kb.

    Your best bet is to investigate the underlying PHP errors that get triggered during the cache purging and then ask the plugin author to take a look.

    I appreciate this isn’t ideal from QM’s point of view but there’s no means of knowing what the header size limit is in order to attempt to stay under it.

    “Your best bet is to investigate the underlying PHP errors that get triggered during the cache purging”

    @johnbillion thanks for your great work! Unfortunately there is no underlying PHP error when this occurs – I have checked the logs very carefully. There is only the Nginx error. Unless you mean that a simple deprecation message is an error in this context?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Causes NGINX Helper to 502 when purging cache’ is closed to new replies.