Auto Expose Ports does not work behind Nginx Reverse Proxy

[Andreas Morgner]

Running the Free Version 2.0.20, the auto expose ports functionally behind a Nginx reverse proxy seams to be broken.

Creating a new Poste Container works well, the WebUI/Admin UI works as expected, but mailing does work internally only or using the webUI. Clients are not able to connect to IMAP/SMTP. A basic telnet returns the error:

telnet mail.domain.com 587
Trying 78.**.**.69...
telnet: connect to address 78.**.**.69: Connection refused

Exposing the mailing ports manually and only auto expose the ports 80/443 fixed the issue and mailing works for clients as well.

With the port mapping shown below everything is working:

0.0.0.0:32967  110/tcp
0.0.0.0:143  143/tcp
0.0.0.0:25  25/tcp
0.0.0.0:4190  4190/tcp
0.0.0.0:32966  443/tcp
0.0.0.0:465  465/tcp
0.0.0.0:587  587/tcp
0.0.0.0:32968  80/tcp
0.0.0.0:993  993/tcp
0.0.0.0:995  995/tcp

[Scott MacDonald]

Per the documentation, if you're not using the "--net=host" directive then you need to specify the individual ports to map.

The configuration is made more complex if you are proxying the webUI.