502 after last update

I don’t see any 502 error on my test version.
Try to delete and install the plugin again.

If doesn’t work, check your php logs for the reason, else I have no idea.

I disabled it first. I rolled back to the previous version. It worked. I was lucky that I had yesterday’s archive of the site.

• This reply was modified 3 years, 7 months ago by eddie.

it still doesn’t explain the reason.
If doesn’t work, check your php logs for the reason, else I have no idea.

Hello,
I also have a 502 error since the update.

The 502 error appears when I am not logged in

It could be the HTTP headers, if your server doesn’t support http2.
In that case, you can disable the option for the Link Preload options or update your server settings.

@alignak server support http2.
I didn’t update again.

But CSS and JS transfer by CDN. I dont now about http2 on Akamai servers.

“Disable JS link preload” was always not selected.

• This reply was modified 3 years, 7 months ago by eddie.

I have the same issue with 502 Bad Gateway after last update.
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.

P.S. Just 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?

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.