• Dear all,

    since recently, but I can’t pin it down exactly as updates went smoothly and in incognito mode it’s not reproducible, I am facing Bad Gateway errors on my nginx. As follows the error log:

    2017/06/15 09:25:53 [error] 9432#9432: *1 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /wp-includes/class-wp-hook.php on line 291
    PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in /wp-content/plugins/w3-total-cache/Util_Content.php on line 1" while reading response header from upstream, client: 46.5.0.99, server: atmedia-marketing.com, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/run/php/php7.0-fpm.sock:", host: "atmedia-marketing.com"
    2017/06/15 09:25:53 [error] 9432#9432: *1 upstream sent too big header while reading response header from upstream, client: 46.5.0.99, server: atmedia-marketing.com, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/run/php/php7.0-fpm.sock:", host: "atmedia-marketing.com"

    Don’t know what’s increasing the header size to 134217728 bytes (>130 MB). Any ideas?

    EDIT: After deleting the cookie “wordpress_logged_in_” it worked again. Something bound to my session but I am certain I have not started working on any pages / posts which could have flooded the cache. Last actions was to update the plugins and the website check afterwards was ok.

    Thanks
    Mike

    • This topic was modified 7 years, 5 months ago by Mike Wiegand.
    • This topic was modified 7 years, 5 months ago by Mike Wiegand.
Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Util_Content.php Upstream sent too big header –?Allowed memory size exhausted’ is closed to new replies.