502 Bad Gateway

  • Resolved sanatolii

    (@sanatolii)


    4 years, 5 months ago

    The plugin helps to identify the IP attacker, but it does not save from a massive attack, there is an increase in memory consumption on the server and, as a result, 502 Bad Gateway. Manual blocking of IP at the level of the .htaccess file saves. It would be better if the plugin wrote blocking rules in .htaccess, this would reduce the load on the server.
    This is a wish !!!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author nintechnet

    (@nintechnet)

    In the premium version, all events can be redirected to the syslog server so that it’s possible to use Fail2ban to block offending IP addresses at the kernel firewall level.
    In the free version, the Login Protection has a similar feature that write the IP to the server’s Authentication log, but only for brute-force attacks

    Thread Starter sanatolii

    (@sanatolii)

    nfwp 4.2.4 ON
    From an attack of this type, the server went into error 502.
    LOG NinjaFirewall
    Manual add to Deny from 52.17.98.131 .htaccess Saved the situation.

    • This reply was modified 4 years, 5 months ago by sanatolii.
    • This reply was modified 4 years, 5 months ago by sanatolii.
    Thread Starter sanatolii

    (@sanatolii)

    I did like this in function nfw_block() after echo add line:

    $ipblock=NFW_REMOTE_ADDR;
$htaccessh = fopen(ABSPATH.'.htaccess', 'a');
fwrite($htaccessh, "\ndeny from $ipblock");
fclose($htaccessh);
    Plugin Author nintechnet

    (@nintechnet)

    What kind of hosting do you have? Is it your own server or a shared hosting plan?
    It looks quite slow, because normally your server should not go down with this attack.

    Thread Starter sanatolii

    (@sanatolii)

    shared hosting plan -250 Mb memory

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘502 Bad Gateway’ is closed to new replies.