• 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 Fire2ban not working with banned IP

Angelo

New Pleskian
Server operating system version
CentOS7
Plesk version and microupdate number
18.0.48
Hi,

I have set up the file2ban rule with jail and filter.

and when I test to run the command:
fail2ban-client set recidive banip [my ip]
and it works, I've checked the iptables -L -n -v
it shows:
Chain f2b-recidive (1 references)
pkts bytes target prot opt in out source destination
0 0 REJECT all -- * * [my ip] 0.0.0.0/0 reject-with icmp-port-unreachable
169K 1809M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0
It seems like working now, but when I try to connect to the server website (port 443)

I am still connected. why?
I don't understand the reason.
 
Thanks for your reply,
I've tried to use this command, and here is the test.
1672711271202.png
It seems like works, but I still can access the server via port 443
 
Back
Top