1

Topic: Upgrade from Iredmail-1.3.1 to Pro v 4.4

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version 1.3.1 MARIADB edition.
- Deployed downloadable installer?
- Linux/BSD distribution Ubuntu 20.04.1 LTS:
- Store mail accounts in which backend (/MySQL/):
- Web server ( Nginx):
- Manage mail accounts with iRedAdmin-Pro
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Upgrade all showed success  Sogo works  https:bla.blah.com/iredadmin  502 Bad Gateway

help

2

Re: Upgrade from Iredmail-1.3.1 to Pro v 4.4

I have the same problem. I first tried install without sudo and it failed, then I immediately tried with sudo and all successful, but iredadmin fails with bad gateway. Roundcube works ok. I had to restore from backup to get working again, but I would like to install the upgrade to PRO. Waiting to see if you get an answer.

3

Re: Upgrade from Iredmail-1.3.1 to Pro v 4.4

william_jmr wrote:

Upgrade all showed success  Sogo works  https:bla.blah.com/iredadmin  502 Bad Gateway

Please visit the iRedAdmin-Pro again, then run commands below immediately and show us the output:

service iredadmin status
tail -20 /var/log/syslog

----

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

buy me a cup of coffee

4

Re: Upgrade from Iredmail-1.3.1 to Pro v 4.4

ZhangHuangbin wrote:
william_jmr wrote:

Upgrade all showed success  Sogo works  https:bla.blah.com/iredadmin  502 Bad Gateway

Please visit the iRedAdmin-Pro again, then run commands below immediately and show us the output:

service iredadmin status
tail -20 /var/log/syslog

Thank you you sorted this morning

5

Re: Upgrade from Iredmail-1.3.1 to Pro v 4.4

What was the solution?

6

Re: Upgrade from Iredmail-1.3.1 to Pro v 4.4

Just had exactly the same problem. Service status shows:

iredadmin.service - iRedAdmin daemon service
     Loaded: loaded (/lib/systemd/system/iredadmin.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2020-08-24 02:28:56 UTC; 14min ago
   Main PID: 21041 (uwsgi)
      Tasks: 6 (limit: 4498)
     Memory: 3.5M
     CGroup: /system.slice/iredadmin.service
             ââ21041 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini --pidfile /v>
             ââ21043 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini --pidfile /v>
             ââ21044 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini --pidfile /v>
             ââ21045 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini --pidfile /v>
             ââ21046 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini --pidfile /v>
             ââ21047 /usr/bin/uwsgi --ini /opt/www/iredadmin/rc_scripts/uwsgi/debian.ini --pidfile /v>

Aug 24 02:28:56 mxserver iredadmin[21041]: spawned uWSGI worker 5 (pid: 21047, cores: 1)
Aug 24 02:29:45 mxserver iredadmin[21041]: -- unavailable modifier requested: 0 --
Aug 24 02:29:53 mxserver iredadmin[21041]: -- unavailable modifier requested: 0 --
Aug 24 02:37:20 mxserver iredadmin[21041]: -- unavailable modifier requested: 0 --
Aug 24 02:37:26 mxserver iredadmin[21041]: -- unavailable modifier requested: 0 --
Aug 24 02:37:28 mxserver iredadmin[21041]: -- unavailable modifier requested: 0 --
Aug 24 02:37:42 mxserver iredadmin[21041]: -- unavailable modifier requested: 0 --
Aug 24 02:42:06 mxserver iredadmin[21041]: -- unavailable modifier requested: 0 --
Aug 24 02:42:29 mxserver iredadmin[21041]: -- unavailable modifier requested: 0 --
Aug 24 02:42:36 mxserver iredadmin[21041]: -- unavailable modifier requested: 0 --

and syslog:

Aug 24 02:35:01 mxserver CRON[22071]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db                                   
Aug 24 02:36:01 mxserver CRON[22114]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db                                   
Aug 24 02:37:01 mxserver CRON[22138]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db                                   
Aug 24 02:37:20 mxserver iredadmin: -- unavailable modifier requested: 0 --
Aug 24 02:37:26 mxserver iredadmin: -- unavailable modifier requested: 0 --
Aug 24 02:37:42 mxserver iredadmin: message repeated 2 times: [ -- unavailable modifier requested: 0 -                                 
Aug 24 02:38:01 mxserver CRON[22163]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db                                   
Aug 24 02:39:01 mxserver CRON[22192]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run                             /systemd/system ]; then /usr/lib/php/sessionclean; fi)
Aug 24 02:39:01 mxserver CRON[22193]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db                                   
Aug 24 02:39:07 mxserver systemd[1]: Starting Clean php session files...
Aug 24 02:39:08 mxserver systemd[1]: phpsessionclean.service: Succeeded.
Aug 24 02:39:08 mxserver systemd[1]: Finished Clean php session files.
Aug 24 02:40:01 mxserver CRON[22287]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db                                   
Aug 24 02:41:01 mxserver CRON[22311]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db                                   
Aug 24 02:42:01 mxserver CRON[22339]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db                                   
Aug 24 02:42:06 mxserver iredadmin: -- unavailable modifier requested: 0 --
Aug 24 02:42:29 mxserver iredadmin: -- unavailable modifier requested: 0 --
Aug 24 02:42:36 mxserver iredadmin: -- unavailable modifier requested: 0 --
Aug 24 02:43:01 mxserver CRON[22377]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db 
Aug 24 02:44:01 mxserver CRON[22410]: (root) CMD (/bin/bash /usr/local/bin/fail2ban_banned_db unban_db