After researching I am quite sure this post is definitely new.
I have a mail client running on one of my VPS (brand new installation and brand new public static IPv4 address - let’s called it A.B.C.D).
While creating a mail account in my mail client - trying to retrieve emails from my existing mailbox in my mail server running on my instance of HestiaCP - I received connection refused.
After a first digging I realized that - for some strange reason (still unknown to me) - the IP address of my server appeared in the list of banned IP addresses in the Manage Banned IPs section of my HestiaCP web admin UI.
Small note: the service appeared as RECIDIVE (screenshot below):
After reading in this forum, I added the following line at the end of the file /etc/fail2ban/jail.local
ignoreip = A.B.C.D E.F.G.H.
Please note also the second IP address (E.F.G.H.) added after leaving a space as per instructions in the file /etc/fail2ban/jail.conf (which I haven’t modified - see screenshot of this file below):
I then restarted the fail2ban service (
# systemctl restart fail2ban) and also did a reboot. After that my banned IP address A.B.C.D. disappeared from the list of banned IP addresses in the HestiaCP web admin UI and I was able to successfully configure my mail client in my VPS with IP address A.B.C.D.
All the above was 24 hours ago.
Today I realized that the IP address A.B.C.D. is banned back again in HestiaCP. I checked the file /etc/fail2ban/jail.local (in case the modification I made yesterday did not survive the previous reboot) but the directive I entered is still there.
Can someone help on this?
HINT: In my HestiaCP web admin UI, the IP address A.B.C.D. appeared as banned, however the value of the service (last column in the right) is now reporting MAIL instead of RECIDIVE:
Thanks in advance.