• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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