1

Topic: All Ports Suddenly Closed

Hi all,

All of the ports of the server on which I installed iRedMail have (with the exception of SSH) suddenly and inexplicably closed:

PORT    STATE  SERVICE
22/tcp  open   ssh
80/tcp  closed http
110/tcp closed pop3
143/tcp closed imap
443/tcp closed https
465/tcp closed smtps
587/tcp closed submission
993/tcp closed imaps
995/tcp closed pop3s

The server was processing mail without a problem for a day or two and then suddenly this. I checked if maybe iptables is responsible, but no rules are active.

root@mx:~# iptables -nvL
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target     prot opt in     out     source               destination 


Deployed with the downloadable installer on Debian 10 with a Postgresql back-end. The webserver is nginx.

iRedMail edition:
1.0 PGSQL edition.

2

Re: All Ports Suddenly Closed

Also, is there some sort of firewall installed with iRedMail by default?

3

Re: All Ports Suddenly Closed

are the services still running? maybe it is banned for ipv6 and not for ipv4?

try ip6tables -nvL

4

Re: All Ports Suddenly Closed

Thanks, Cthulhu, but the answer was much simpler than that. It looks like the problem was that fail2ban was doing its job... roll

Anyhow, iRedMail is absolutely fantastic. The amount of work put into it is quite phenomenal.

I don't really need a support contract, but the project is definitely worthy of a donation. Is there any way that I can do that?