• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue 600 requests in one second: How to prevent this attack

ahoi

Basic Pleskian
Hello everybody,

one of my servers is facing recurring "attacks" like this:


Bash:
/var/log/nginx/access.log
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /backup HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /newsite HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET / HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /old HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /test HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /wordpress HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /wp HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /cms HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /main HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /blog HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /new HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /dev HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /cms HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /new HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /blog HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /backup HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /dev HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /dev HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /main HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /newsite HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /cms HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /backup HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET / HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /wp HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET /old HTTP/1.1" 301 162 "-" "-"
46.xx.138.xx - - [19/Aug/2021:02:49:16 +0200] "GET / HTTP/1.1" 301 162 "-" "-"

I truncated the full logs, but altogether there are more than 1000 requests made in one or two seconds.

I am thinking about some rate-limiting using iptables, but maybe Plesk is already providing something built-in which I did not found out yet?

Love to get some advice :)
 
Back
Top