1 Topic by 1day (edited by 1day 2019-05-28 12:44:18)

  • 1day
  • Member
  • Offline
  • Registered: 2019-05-28
  • Posts: 2

Topic: roundcube gives me 502 Bad Gateway and can't login in SoGo

iRedMail  0.9.9 downloadable on Debian 9 with MariaDB and Nginx

1./mail/ gives me 502 Bad Gateway :
2019/05/27 21:17:29 [error] 1033#1033: *124 connect() failed (111: Connection refused) while connecting to upstream, client:1.1.1.1, server: _, request: "GET /mail/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999"
Everything else is working.

2. Can't log in to SOGo - Wrong username or password:

SOGoRootPage Login from '1.1.1.1' for user 'sogo_sieve_master@not-exist.com' might not have worked - password policy: 65535  grace: -1  expire: -1  bound: 0

----

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

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: roundcube gives me 502 Bad Gateway and can't login in SoGo

1: php-fpm service is not running.
2: "sogo_sieve_master@not-exist.com" is a dovecot master user, you can not login as this user directly. FYI: https://docs.iredmail.org/dovecot.master.user.html

3 Reply by 1day (edited by 1day 2019-06-01 13:35:24)

  • 1day
  • Member
  • Offline
  • Registered: 2019-05-28
  • Posts: 2

Re: roundcube gives me 502 Bad Gateway and can't login in SoGo

1. SOLVED by changing "fastcgi_pass php_workers;" to "fastcgi_pass unix:/run/php/php7.0-fpm.sock;" in /etc/nginx/templates/fastcgi_php.tmpl

2. I created a new account in iredmail and was able to log in with it.

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: roundcube gives me 502 Bad Gateway and can't login in SoGo

1day wrote:

1. SOLVED by changing "fastcgi_pass php_workers;" to "fastcgi_pass unix:/run/php/php7.0-fpm.sock;" in /etc/nginx/templates/fastcgi_php.tmpl

You should update /etc/nginx/conf-enabled/php-fpm.conf to use socket by still keep the upstream name "php_workers", not update /etc/nginx/templates/*.conf to use socket path directly.