• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs Fail2ban can't create custom jails with custom filter

Azurel

Silver Pleskian
User name: Azurel

TITLE

Fail2ban can't create custom jails with custom filter

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CentOS 8.2, Plesk Obsidian 18.0.29#1

PROBLEM DESCRIPTION

CentOS 8.2 with Obsidian 18.0.29#1

I want create a custom jail. First I added a jail filter "custom-filter"
[Definition]
failregex = <HOST>$
ignoreregex =

Now I want add a jail with this custom filter
* Name: custom_jail
* Filter: custom-filter (selectbox)
* Action: iptables-allports[chain="INPUT", name="default", port="ssh", protocol="tcp", blocktype="REJECT --reject-with icmp-port-unreachable", returntype="RETURN", lockingopt="-w", iptables="iptables <lockingopt>"]
* Log path: /mypath...
* ban period: 172800
* login attempts: 1

After press save button I get this
Error: f2bmng failed: 2020-08-13 10:01:28,682 fail2ban.configreader [341671]: ERROR Found no accessible config files for 'filter.d/custom-filter' under /etc/fail2ban
2020-08-13 10:01:28,682 fail2ban.jailreader [341671]: ERROR Unable to read the filter 'custom-filter'
2020-08-13 10:01:28,682 fail2ban.jailsreader [341671]: ERROR Errors in jail 'custom_jail'. Skipping...
ERROR:__main__:Command '['/usr/bin/fail2ban-client', 'reload', '--if-exists', 'custom_jail']' returned non-zero exit status 255
ERROR:__main__:Failed to reload following jails due to errors in configuration: custom_jail

There is the file /etc/fail2ban/filter.d/custom-filter.local with correct content.

On old Server CentOS 7.8 its have worked long time ago. What can I do?

STEPS TO REPRODUCE

See description

ACTUAL RESULT

See description

EXPECTED RESULT

Obviously, I want save it :)

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM


Confirm bug
 
From developer:

Unable to reproduce with STR provided by customer (checked on CentOS7 && CentOS8)

So, contact Plesk Support Team. Investigation directly on your server is required.
 
Back
Top