502 Bad Gateway on sites running ngnx after 3.1.6 updade

  • Resolved broslavski

    (@broslavski)


    3 years, 7 months ago

    I have the issue with 502 Bad Gateway after last updates.
    This happens after you clear the cache. The first time the page loads, it gives an error 502, but the second load of the page goes fine.

    Checked with plugin version 3.1.4. There are no problems. The problem starts with version 3.1.6. Version 3.1.7 also causes a 502 error.

    Here is the server log for this error:

    [error] 32350#32350: *82355822 upstream sent too big header while reading response header from upstream, client: XXX.XXX.XXX.XXX, server: mydomain.com, request: "GET /page HTTP/2.0", upstream: "fastcgi://unix:/var/www/php-fpm/mydomain.sock:", host: "mydomain.com"

    Tested the latest version of the plugin on a site that runs on Apache and found no 502 errors.

    How can this problem be solved on the last plugin version on sites that run on ngnx?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Raul P.

    (@alignak)

    The latest few FVM versions added support for http2 headers. This will include the reference for the render css and js file urls in the http header.

    If you have a lot of css and js files and are not merging files, this list can be large.

    It works on Apache, but it will trigger an error on nginx because you haven’t configured it properly. Your limit for the http headers size is simply too low, so you need to adjust those settings or ask your hosting to do it for you.

    The size will depend on how many css and js files you need.

    https://www.cyberciti.biz/faq/nginx-upstream-sent-too-big-header-while-reading-response-header-from-upstream/

    Alternatively, you can disable css and js link preloading on the plugin settings.

    Thread Starter broslavski

    (@broslavski)

    @alignak Thank you! I’ll try to figure out the limits and let you know if it helped.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘502 Bad Gateway on sites running ngnx after 3.1.6 updade’ is closed to new replies.