• 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 Unable To turn on Fail2Ban , Nothing In Logs

rushaboswal

New Pleskian
Im trying to turn on fail2ban but it starts and shutsdown again.
Server Info - Plesk Obsidian v18.0.40_build1800211230.16 os_Ubuntu 20.04
This is the log i get
2022-01-12 08:19:11,083 fail2ban.server [883]: INFO --------------------------------------------------
2022-01-12 08:19:11,083 fail2ban.server [883]: INFO Starting Fail2ban v0.11.1
2022-01-12 08:19:11,084 fail2ban.observer [883]: INFO Observer start...
2022-01-12 08:19:11,100 fail2ban.database [883]: INFO Connected to fail2ban persistent database '/var/lib/fail2ban/fail2ban.sqlite3'
2022-01-12 08:19:11,106 fail2ban.jail [883]: INFO Creating new jail 'sshd'
2022-01-12 08:19:11,142 fail2ban.jail [883]: INFO Jail 'sshd' uses pyinotify {}
2022-01-12 08:19:11,153 fail2ban.jail [883]: INFO Initiated 'pyinotify' backend
2022-01-12 08:19:11,155 fail2ban.filter [883]: INFO maxLines: 1
2022-01-12 08:19:11,174 fail2ban.filter [883]: INFO maxRetry: 5
2022-01-12 08:19:11,175 fail2ban.filter [883]: INFO findtime: 600
2022-01-12 08:19:11,175 fail2ban.actions [883]: INFO banTime: 600
2022-01-12 08:19:11,175 fail2ban.filter [883]: INFO encoding: UTF-8
2022-01-12 08:19:11,175 fail2ban.filter [883]: INFO Added logfile: '/var/log/auth.log' (pos = 2929, hash = 92232f7a7596ea20e9879b628261acbc12a82033)
2022-01-12 08:19:11,180 fail2ban.jail [883]: INFO Jail 'sshd' started
2022-01-12 08:19:11,183 fail2ban.server [883]: INFO rollover performed on /var/log/fail2ban.log
2022-01-12 08:20:02,355 fail2ban.filter [883]: INFO [sshd] Found 143.244.148.248 - 2022-01-12 08:20:01
2022-01-12 08:21:39,450 fail2ban.server [883]: INFO Shutdown in progress...
2022-01-12 08:21:39,450 fail2ban.observer [883]: INFO Observer stop ... try to end queue 5 seconds
2022-01-12 08:21:39,471 fail2ban.observer [883]: INFO Observer stopped, 0 events remaining.
2022-01-12 08:21:39,512 fail2ban.server [883]: INFO Stopping all jails
2022-01-12 08:21:39,513 fail2ban.filter [883]: INFO Removed logfile: '/var/log/auth.log'
2022-01-12 08:21:39,561 fail2ban.actions [883]: NOTICE [sshd] Flush ticket(s) with iptables-multiport
2022-01-12 08:21:39,561 fail2ban.jail [883]: INFO Jail 'sshd' stopped
2022-01-12 08:21:39,562 fail2ban.database [883]: INFO Connection to database closed.
2022-01-12 08:21:39,562 fail2ban.server [883]: INFO Exiting Fail2ban
 
Back
Top