• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Error activating Fail2Ban

Goodnight:

I am trying to activate Fail2Ban from the Plesk Panel, but I always get this error message:

Error: Failed to save settings:f2bmng failed: Job for fail2ban.service failed because the control process exited with error code. See "systemctl status fail2ban.service" and "journalctl -xe" for details.
ERROR:f2bmng:Failed to start fail2ban service

Captura_de_pantalla_6.png


Command #service fail2ban status

[root@mydomain ~]# service fail2ban status
Redirecting to /bin/systemctl status fail2ban.service
● fail2ban.service - Fail2ban Service
Loaded: loaded (/etc/systemd/system/fail2ban.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Tue 2016-11-08 00:22:32 CET; 6min ago
Process: 3258 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)

Nov 08 00:22:32 mydomain.com systemd[1]: fail2ban.service: control process exited, code=exited status=255
Nov 08 00:22:32 mydomain.com systemd[1]: Failed to start Fail2ban Service.
Nov 08 00:22:32 mydomain.com systemd[1]: Unit fail2ban.service entered failed state.
Nov 08 00:22:32 mydomain.com systemd[1]: fail2ban.service failed.
Nov 08 00:22:32 mydomain.com systemd[1]: fail2ban.service holdoff time over, scheduling restart.
Nov 08 00:22:32 mydomain.com systemd[1]: start request repeated too quickly for fail2ban.service
Nov 08 00:22:32 mydomain.com systemd[1]: Failed to start Fail2ban Service.
Nov 08 00:22:32 mydomain.com systemd[1]: Unit fail2ban.service entered failed state.
Nov 08 00:22:32 mydomain.com systemd[1]: fail2ban.service failed.


Where the problem lies?

A greeting and thanks in advance.
 
Hi jorgemartincasasola,

pls. see as well depending log - entries from "/var/log/fail2ban.log" and don't forget the second suggestion from your error - message for investigations reasons:
See "systemctl status fail2ban.service" and "journalctl -xe" for details.

In addition, it would really help if you would provide informations about:
  • Your operating system
  • Your current Plesk version ( incl. MU )


A common reason why Fail2Ban can't start is the absent directory "/var/run/fail2ban". Pls. make sure that the directory exists and that it has the correct permissions ( 0755 / user: root / group: root ).
Code:
COMMAND TO USE OVER THE COMMAND LINE - logged in as user "root":

mkdir -p /var/run/fail2ban

Another common reason might be the missing file "/var/log/fail2ban.log". Pls. consider to create it manually with for example:
Code:
COMMAND TO USE OVER THE COMMAND LINE - logged in as user "root":

touch /var/log/fail2ban.log
 
Back
Top