1

Topic: Fail2Ban keeps triggering on new install and locking my out

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):  0.9.7
- Deployed with iRedMail Easy or the downloadable installer? No
- Linux/BSD distribution name and version:  Ubuntu 16.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

I moved my email server away from Woothosting/AlphaRacks - their datacenter is presently dead (google the drama for yourselves if you prefer).  I bought a server from flipperhost.com

I tried to set up 0.9.9, but the install fails on an ngix portion.  I reinstalled 0.9.7 which is what I had before.
The install went fine and I updated my DNS records - mail comes in and goes out.

However, fail2ban keeps tripping on the home IP.

I have set ignoreip to both the current physical IP as well as my DDNS name.
The jailing at first was on the jail for the web browswer - easy enough to fix via ssh.

However, I'm now banned for ssh access - this is bad.

So, how, once I get ssh access back (hopefully), do I track down the problem?

Andrew

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Fail2Ban keeps triggering on new install and locking my out

I've added a line in jail.local to see if that fixes the problem.

3

Re: Fail2Ban keeps triggering on new install and locking my out

Better turn on debug mode in Fail2ban and track down the issue.