Bobcares

“Found no accessible config files” error in fail2ban

by | Jan 15, 2022

Wondering how to resolve “Found no accessible config files” error in fail2ban? We can help you.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team help a customer  deal with this Plesk error.

How to resolve “Found no accessible config files” error in fail2ban?

Fail2Ban is an intrusion prevention software framework that protects computer servers from brute-force attacks. Written in the Python programming language.

It is able to run on POSIX systems that have an interface to a packet-control system or firewall installed locally.

“Switch On” Button is either missing or it does not activate jails at Tools & Settings > IP Address Banning.

Fail2Ban is not active at Tools & Settings > Services Management.

Typically, error looks as shown below:

vps-53a4494f fail2ban-server[19023]: fail2ban.configreader [19023]: ERROR Found no accessible config files for ‘filter.d/murmur’ under /etc/fail2ban
vps-53a4494f fail2ban-server[19023]: fail2ban.jailreader [19023]: ERROR Unable to read the filter ‘murmur’
vps-53a4494f fail2ban-server[19023]: fail2ban.jailsreader [19023]: ERROR Errors in jail ‘murmur’. Skipping…
vps-53a4494f fail2ban-server[19023]: fail2ban.jailreader [19023]: ERROR No file(s) found for glob /var/log/proftpd/proftpd.log
vps-53a4494f fail2ban-server[19023]: fail2ban [19023]: ERROR Failed during configuration: Have not found any log file for proftpd jail
vps-53a4494f fail2ban-server[19023]: fail2ban [19023]: ERROR Async configuration of server failed
vps-53a4494f fail2ban-client[19027]: fail2ban [19027]: ERROR Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?

Fail2Ban scans for log services installed on the server.

It cannot start if there are activated jails for packages that are not install.

Today, let us see the steps followed by our Support Techs to resolve it.

1. Firstly, log into Plesk
2. Then, go to the Tools & Settings > IP Address Banning.
3. Then, switch off the unnecessary jail/jails.
4. Finally, start Fail2Ban at Tools & Settings > Services Management.

[Need a solution to another query? We are just a click away.]

Conclusion

Today, we saw steps followed by our Support Engineers to resolve error in fail2ban.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.