• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Fail2Ban custom jail for Ngnix 404 error

Mnu555

New Pleskian
Hi everyone.
Trying to create a custom jail for Fail2ban.
The task is to block bots that access non-existent URLs, which Ngnix gives 404 error.
Unfortunately, I can't get this rule to work.
I am using Plesk Onyx in Centos 7.
Added filter All-404:
Code:
[Definition]
failregex = ^<HOST>.*"(GET|POST).*" (404|444|403|400) .*$
ignoreregex =
And Jail:
Code:
[All-404]
enabled = true
filter = All-404
action = iptables-allports[chain="INPUT", name="default", port="http,https", protocol="tcp", returntype="RETURN", lockingopt="-w"]
logpath = /var/www/vhosts/system/*/logs/proxy_error_log
maxretry = 3
What am I doing wrong ?
 
Back
Top