1

Topic: iRedMail on AWS - ubuntu 18.04 - can't reach server after reboot

iRedMail-0.9.9
downloadable installer
Ubuntu 18.04 AWS AMI
- Store mail accounts in which backend (LDAP
- Web server (Nginx):
- Manage mail accounts with iRedAdmin-Pro? - didn't get that far

When I get to the end of the install everything seems okay. The instruction is to reboot at that point and after that I am no longer able to access the instance. Someone posted that he had similar trouble and that port 22 was shut off so I ran nmap and got this:
Starting Nmap 7.70 ( https://nmap.org ) at 2019-05-25 21:06 PDT
Nmap scan report for ec2-52-53-99-105.us-west-1.compute.amazonaws.com (52.53.99.105)
Host is up (0.057s latency).
Not shown: 89 filtered ports
PORT     STATE  SERVICE
21/tcp   open   ftp
22/tcp   open   ssh
80/tcp   open   http
110/tcp  closed pop3
143/tcp  closed imap
443/tcp  open   https
465/tcp  closed smtps
554/tcp  open   rtsp
993/tcp  closed imaps
995/tcp  closed pop3s
7070/tcp open   realserver
So ssh seems to be open. What am I doing wrong?

----

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

2

Re: iRedMail on AWS - ubuntu 18.04 - can't reach server after reboot

Try to stop "fail2ban" service and try again.

3

Re: iRedMail on AWS - ubuntu 18.04 - can't reach server after reboot

ZhangHuangbin wrote:

Try to stop "fail2ban" service and try again.

Not sure what you mean, if I stop the service before rebooting it will only be restarted when I reboot.

If I disable the service then I need to find out what it does as this server is exposed to the public internet and fail2ban sounds like a security service of some kind.

Thanks for your input - if this works I will buy you a cup of coffee.

4

Re: iRedMail on AWS - ubuntu 18.04 - can't reach server after reboot

Use your AWS console to login to server, then disable the "fail2ban" service, try to login via ssh from external network, e.g. your laptop.