1 (edited by kaipanoi 2015-06-30 05:59:34)

Topic: 502 Bad Gateway when trying to access iRedAdmin on Nginx

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.2

- Linux/BSD distribution name and version: CentOS release 6.6 (Final)

- Store mail accounts in which backend (LDAP/MySQL/PGSQL):  LDAP

- Web server (Apache or Nginx): Nginx

- Manage mail accounts with iRedAdmin-Pro? No

- Related log if you're reporting an issue:
====

I just wanted to share. I got a 502 attempting to connect to iRedAdmin after installing 0.9.2 (and after rebooting) on CentOS 6.6. I chose nginx/ldap/SOGo during installation. I noticed uwsgi could not start. SELINUX was disabled and firewalld was masked and stopped. I found that there was no log dir for it, so I made one:

mkdir /var/log/uswgi
chown -R uwsgi /var/log/uwsgi
service uwsgi start

After that, no issues.

----

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

2

Re: 502 Bad Gateway when trying to access iRedAdmin on Nginx

My mistake, iRedMail doesn't create /var/log/uwsgi. Will fix this in next release.

3

Re: 502 Bad Gateway when trying to access iRedAdmin on Nginx

Great, thank you.