• 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.

Resolved fail2ban no config files /etc/fail2ban/ is empty

G

Gjimi

Basic Pleskian
Server operating system version
Debian 11.11
Plesk version and microupdate number
Plesk Obsidian 18.0.67 Update 2
I have reinstalled fail2ban, uninstalled via web interface, reinstalled via CLI, tried everything, it installed normally, but the /etc/fail2ban/ folder is empty, with no config files.
 
it's been resolved, this was helpful if anyone has the same problem:
apt-get remove --purge fail2ban
then install again via web interface
 
You must log in or register to reply here.

Similar threads

M
Question f2bmng failed: ERROR:__main__:'utf-8' codec can't decode byte 0xfc in position 496: invalid start byte
Replies
4
Views
416
millerbln
M
marcelhalls
Resolved Almalinux - Fail2Ban - Dont Start - BUG ?
Replies
1
Views
677
marcelhalls
marcelhalls
Jürgen_T
Issue How to properly configure Fail2Ban for ModSecurity in Plesk with NGINX?
Replies
5
Views
801
klodoma
K
M
Issue Cannot update packages
Replies
4
Views
707
Raul A.
R
S
Question Abonnements in Monotoring empty
Replies
2
Views
393
shopuser
S
Back
Top