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

Oliver Marugg

Basic Pleskian
Hi
Plesk 12.5.30-37 ubuntu14.04:

a. In fail2ban.log I have following error_:
fail2ban.filter [1506]: WARNING Error decoding line from '/var/log/mail.log' with 'ANSI_X3.4-1968'. Consider setting logencoding=utf-8 (or another appropriate encoding) for this jail. Continuing to process line ignoring invalid characters:

/etc/fail2ban/jails.local
added logencoding=utf-8
I've restarted fail2ban, but cant say if it works now. Because no new log entries are shown.

b. I tried to enter logencoding=utf-8 into fail2ban jail "plesk-dovecot". But no success.

Any ideas?

Many thanks,

oliver
 
I received the same message a few days ago. Seems like Fail2Ban can't read some characters in the log or something like that.
 
Hi Oliver Marugg,

consider to use inside the DEFAULT - section at "/etc/fail2ban/jail.conf" :

Code:
...
[DEFAULT]
...
# "logencoding" specifies the encoding of the log files handled by the jail
#   This is used to decode the lines from the log file.
#   Typical examples:  "ascii", "utf-8"
#
#   auto:   will use the system locale setting
# logencoding = auto
logencoding = utf-8
...

... to avoid entries in several jails, which are "normally" setup with UTF-8 - encoding in their corresponding service - configuration - files by default. Pls. check as well your "system locale settings" and always restart Fail2Ban, if you changed a standart setting.
 
Hi MMagnani,

you can certainly use as well "/etc/fail2ban/jail.local", to make sure, that no (automatic ) updates/upgrades/patches overwrite your setting.
 
Back
Top