Related

Tool Instant DNS Lookup Tool Tool
NGINX Config Generator Tool
Connect to DB installed into dedicated VPS (private networking) Question Question
blocked ip in spam Question Question

Question

NGINX NOT properly set up with iRedMail installation - 502 bad gateway error

Posted October 17, 2020 83 views
NginxEmailDNSLEMPInitial Server Setup

=========================
OS: Linux Ubuntu 20.04
Web server: NGINX
Database: MariaDB

The installer ran on the command line

I have already made the necessary configuration prior to the installation:

  • Set DNS records (A & MX records)

  • Set FQDN with setting the ’/etc/hosts’ file as
    MyIPAddress mail.MyWebsite.com mail

  • Allowed UFW ports 25, 587, 465

  • etc., etc..

Then when I try to go to the login pages for iRedMail & RoundCube, I get nothing but a ‘502 bad gateway’ error page.

I thought that iRedMail says to NOT install anything prior to running their installation. I know that their installation is supposed to be a on 'fresh OS’.

Why doesn’t the installation lead me to a working page? What else could I be missing? Am I still supposed to set up my own NGINX Server Blocks and enable sites on this subdomain?

Any support is appreciated.

Add a comment
AaronEsteban1
By:
AaronEsteban1
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
bobbyiliev 1 day ago

Hi @AaronEsteban1,

In order to get more information about the actual problem, I would suggest checking the Nginx error log, that way you would be able to see what actually is wrong rather than the generic 502 error.

To do that you can run the following command:

  • sudo tail -100 /var/log/nginx/error.log

Also, can you share the installer command that you ran initially?

Regards,
Bobby

Reply Report
  • AaronEsteban1 1 day ago

    Thanks for your reply. I’ve already solved this issue. The problem was that I forgot to ‘reboot’ the system after the installation in order to fix the access to logging in. Everything worked after rebooting.

    Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help