Failed to read FastCGI header

  • Resolved molden

    (@molden)


    7 years, 10 months ago

    Error dispatching request to :
    Failed to read FastCGI header, referer: https://www.sincitymunitions.com/wp-admin/admin-ajax.php?action=wp_ewwwio_media_optimize&nonce=df795df9c2

    This plugin causes very slow PHP response times ultimately choking out the WP and is blocking Events Espresso plugins with this error:
    preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 662\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 662\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 662\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 662\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 662\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 662\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 662\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 662\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 662\nPHP message: PHP Warning: preg_match() expects parameter 2 to be string, array given in /var/www/wordpress/wp-content/plugins/event-espresso-core-reg/core/third_party_libs/pue/pue-client.php on line 662\n’, referer: https://www.sincitymunitions.com/wp-admin/admin-ajax.php?action=wp_ewwwio_media_optimize&nonce=df795df9c2

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter molden

    (@molden)

    https://serverpilot.io/community/articles/error-failed-to-read-fastcgi-header.html

    Suggests the problem lies with this plugin and not Events Espresso.

    Also, when this plugin is deactivated EE works as expected and the numerous preg_match() errors cease as do the FastCGI headers errors.

    Thread Starter molden

    (@molden)

    And when EWWW Image Optimizer is active, PHP response times rocket up to +25,000 ms per request eventually choking out the server altogether – site starts responding with 503.

    When EWWW Image Optimizer disabled response times drop to +/-7,680 ms peak and down to +/-500 ms but is responsive nonetheless.

    • This reply was modified 7 years, 10 months ago by molden.
    Plugin Author nosilver4u

    (@nosilver4u)

    Those requests are from EWWW attempting to optimize your uploads ‘in the background’, and the fact that EE is throwing crazy errors during the resulting call to admin-ajax.php indicates EE is doing something weird, but I’ve never used EE, so I have no idea what it could even be. As you did with EWWW, I suspect if you disable EE, things would work just fine as well, but there is some interaction between the two that brings things to a halt.

    Thread Starter molden

    (@molden)

    Testing validates this; if one is disabled the other works without errors.

    I have used EE for a year now and a dev installed EWWW just recently. I guess we will have to remove EWWW.

    Plugin Author nosilver4u

    (@nosilver4u)

    that’s a shame, I’d be willing to see if we can find the trigger for the problem, hit me up here if you want to dig into it further: https://ewww.io/contact-us/

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Failed to read FastCGI header’ is closed to new replies.