|
TownCountry
|
November 29, 2018 at 7:31 am
If I use the Filtered CSV Export Button I always get a 502 error.
|
|
Josh
|
November 29, 2018 at 7:46 am
The main reason you’ll see a 502 bad gateway error is due to an issue with the web host. Sometimes a query, script, or request will take too long and so it is canceled or killed by the server. A lot of hosts, especially shared hosts add what they call a “kill script.” Basically what this does is it will terminate a request after a certain period of time so that it doesn’t take a site down or impact other users.
Since we don’t know for sure whether your host has a kill script in place, your can try this troubleshooting method:
Try temporarily deactivating all other plugins on the site and try those links again. If no Bad Gateway error with all other plugins deactivate, you reactivate the other plugins one-by-one until the you see the error again.
|
|
TownCountry
|
November 29, 2018 at 8:20 am
After trying something, I think it’s related to the nginx cache. Do you know that problem?
|
|
Josh
|
November 29, 2018 at 8:24 am
I do not. You could check with your web host, they might know what to do.
|
|
TownCountry
|
December 6, 2018 at 5:19 am
I found an error log in the proxy_error_log:
“upstream sent too big header while reading response header from upstream”
I think this is the problem. Can you fix this?
|
|
Josh
|
December 6, 2018 at 6:36 am
No. This is something your web host will have to fix. Here’s one (of many) references that explains how:
https://andrewlock.net/fixing-nginx-upstream-sent-too-big-header-error-when-running-an-ingress-controller-in-kubernetes/
|
