502 Bad Gateway

  • Resolved sachtbm

    (@sachtbm)


    3 years, 7 months ago

    Since last 2 upgrades, I started receiving 502 Bad Gateway on the site, so had to rollback to old version.

    Logs show this error;
    WARNING: [pool www] child 60982 exited on signal 11 (SIGSEGV – core dumped) after 0.727208 seconds from start

    Is there any solution to the issue? Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter sachtbm

    (@sachtbm)

    I believe it has something to do with the timing of amp_is_request being called. Removed it from ‘init’ action and ‘clean_url’ filter. The site started working.

    Plugin Support Milind More

    (@milindmore22)

    Hello @sachtbm

    Thank you for debugging and letting us know about the issue, we will make note of it for future reference.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘502 Bad Gateway’ is closed to new replies.