Is this an attack or a normal request?
jeff.dyke at gmail.com
Wed Aug 26 02:30:38 UTC 2020
I've seen the rest of this thread, and there are many good ideas, fail2ban
is great, i actually use it with wazuh. The best security measure i ever
made with wordpress is changing the name of the /admin/login.php and
disabling or at least access listing the api. If no one needs api access,
shut it off. With fail2ban with wazuh, perhaps fail2band handles this on
its own, you can set up volume rules which will create FW rules. Also, i
like to put in a snippit into nginx config for to many responses.
limit_req_zone $limit_key zone=req_limit:10m rate=10r/s;
# don't use 503 as we have specific logic for that status
As the comment says we handle 503's and other status codes differently, so
i adopted Twitters Ease You Calm status code. Change the limits to your
On Mon, Aug 24, 2020 at 7:23 AM Anderson dos Santos Donda <
andersondonda at gmail.com> wrote:
> Hello everyone,
> I’m new in the webserver world, and I have a very basic knowledge about
> Nginx, so I want apologize in advance if I'm making a stupid question.
> I have a very basic webserver hosting a WordPress webpage and in the past
> 3 days I have receiving thousands of below request:
> 220.127.116.11 - - [24/Aug/2020:12:30:41 +0200]
> 18.104.22.168 - - [24/Aug/2020:12:30:41 +0200] "P\xCE
> 400 173 "-" "-”
> This comes from a hundred of different IPs and in many requests at same
> Is this kind of DDOS attack or a legitimate request(which my server
> returns 400 for them)?
> If is an attack, has a specific name that I can search and try to
> understand it better and mitigate it?
> Thank so much for the help.
> Best Regards,
> Anderson Donda
> *" **Mar calmo não cria bom marinheiro, muito menos bom capitão.**"*
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx