Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter jlee2027

    (@jlee2027)

    Ok, the 499 is solved. It was a PHP Pool issue where pm.max.children was 5. Rather silly that the default PHP would set itself to only 5 instances but I digress. When it reached a need for 6, it waited 30 seconds, then NGINX timed it out. I increased the pm.max.children, rebuilt PHP (reboot will not do it, you must rebuild) and the 499 is gone.

    Thank you all for your support Caleb and wfyAnn, definitely helped!

    I’m still getting
    2017-08-26 08:34:47 Error 219.85.235.75 405 GET /xmlrpc.php HTTP/1.1
    2017-08-26 08:34:49 Error 219.85.235.75 503 GET /wp-login.php HTTP/1.1
    2017-08-26 08:34:49 Error 219.85.235.75 503 GET /wp-login.php HTTP/1.1
    2017-08-26 08:34:50 Error 219.85.235.75 503 GET /wp-login.php HTTP/1.1
    2017-08-26 08:34:53 Error 219.85.235.75 503 GET /wp-login.php HTTP/1.1

    Ignore the 405 and 503. I’m telling WordPress what to send them hopefully to discourage them from hitting our server, but regular attempts with different IP’s are still happening.

    Is there a way to block these attempts? TIA.

    • This reply was modified 7 years, 3 months ago by jlee2027.
    Thread Starter jlee2027

    (@jlee2027)

    And down again….

Viewing 2 replies - 1 through 2 (of 2 total)