• ResolvedModerator Bet Hannon

    (@bethannon1)


    My host has informed me that I’ve been using excessive resources, and it appears that there are a lot of admin-ajax.php calls for multiple sites.

    I don’t think I have any of the plugins that might cause this, but I have seen the mention of deregistering WP Heartbeat as one way to bring down the usage of admin-ajax.php.

    Is this advisable in multisite? Does putting the dereg code in the main site’s functions.php deregister heartbeat network-wide?

    Other things I should be looking for in troubleshooting the heavy calls to this file?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator Bet Hannon

    (@bethannon1)

    Ah… Might be a WordFence issue. I seem to be having a lot of attempts at wp-login.php that WF is blocking/throttling. Checking on that, but welcoming other thoughts.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    WordFence would be my best bet :/

    It’s great, btu it’s heavy.

    Moderator Bet Hannon

    (@bethannon1)

    I did figure out that we were having a brute force attack. WordFence was blocking 80-100 login attempts per minute for a most of yesterday.

    Media Temple suggested taking the worst offending IP addresses and blocking them in htaccess so that they never reached php and eat up the server resources. This seems to have helped. Or at least we aren’t having as many blocks needed today.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Ask MediaTemple if they have Fail2Ban or CSF with iptables installed to hook into ModSecurity? That’s going to be WAY better than a plugin if they configure those to auto-block.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘heavy admin-ajax.php usage’ is closed to new replies.