1

Topic: [iRedMail] Connection refused after 0.9.9 update

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

Hi,

First of all it is for me the opportunity to thank you very much for what you do: Thank you

Everything worked perfectly until I did the update from 0.9.8 to 0.9.9.
I followed this tutorial : https://docs.iredmail.org/upgrade.iredm … 0.9.9.html
(Except LDAP parts)

Now I can reach the roundcube login page, but when I try to connect here is the error I have in logs :

May 12 14:59:54 vps000000 roundcube: PHP Warning:  stream_socket_client(): unable to connect to 127.0.0.1:143 (Connection refused) in /opt/www/roundcubemail-1.3.6/program/lib/Roundcube/rcube_imap_generic.php on line 959
May 12 14:59:54 vps000000 roundcube: <r097nvf2> IMAP Error: Login failed for info@domain.com from 78.238.xxx.xxx. Could not connect to 127.0.0.1:143: Connection refused in /opt/www/roundcubemail-1.3.6/program/lib/Roundcube/rcube_imap.php on line 196 (POST /mail/?_task=login&_action=login)

Telnet return this :

root@vps000000:/etc/fail2ban# telnet localhost 143
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

iptables return this :

root@vps000000:/etc/fail2ban# iptables -L -n
Chain INPUT (policy DROP)
target     prot opt source               destination
f2b-postfix  tcp  --  0.0.0.0/0            0.0.0.0/0            multiport dports 80,443,25,587,110,995,143,993,4190
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state RELATED,ESTABLISHED
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0            icmptype 8
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:22
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:80
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:443
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:25
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:587
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:110
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:995
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:143
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:993

Chain FORWARD (policy DROP)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain f2b-postfix (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Any suggestion please ?
Thx

2

Re: [iRedMail] Connection refused after 0.9.9 update

Seems Dovecot service is not running. try to restart "dovecot" service and it should be fine.
Pay attention to Dovecot log file /var/log/dovecot/*.log, if there's something wrong with Dovecot config file, it will be logged.

----

Does my reply help a little? How about buying me a cup of coffee ($5) as an encouragement?

buy me a cup of coffee

3

Re: [iRedMail] Connection refused after 0.9.9 update

ZhangHuangbin wrote:

Seems Dovecot service is not running. try to restart "dovecot" service and it should be fine.
Pay attention to Dovecot log file /var/log/dovecot/*.log, if there's something wrong with Dovecot config file, it will be logged.

Woaw ! Nice !

I changed certbot certs for a new wildcard one and I forgot to replace path in dovecot conf file. That's why Dovecot do not wanted to start.

Thank you so much.
Regard