• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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