[AFTER LAST UPDATE] upstream sent too big header while reading response header f
-
I’ve just updated to the last version of LiteSpeed Cache and my pages started returning 502 Bad Gateway addons. I’ve checked my error log and it gave me “upstream sent too big header while reading response header from upstream”.
The problem was gone when I disabled the LiteSpeed Cache plugin
Viewing 9 replies - 1 through 9 (of 9 total)
Viewing 9 replies - 1 through 9 (of 9 total)
- The topic ‘[AFTER LAST UPDATE] upstream sent too big header while reading response header f’ is closed to new replies.