[MM3-users] Re: nginx configuration on a multitasking server

On 12/10/21 12:57 PM, Mark Sapiro wrote:

On 12/10/21 10:22 AM, David Newman wrote:

...

1. At least on my system, the proxy_pass statement will only run without errors if I change this to a fully formed URL, e.g., 'proxy_pass http://127.0.0.1:8000'. Is this a typo in the docs?

I changed it at https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configurat... but I wonder if we shouldn't be using uwsgi_pass instead of proxy_pass.

See https://nginx.org/en/docs/http/ngx_http_uwsgi_module.html#uwsgi_pass

Are you using uwsgi or some other wsgi server.

uwsgi, per the venv and PDF docs. Thanks for the fix.

Regarding the uwsgi_pass docs, would 'uwsgi_pass_header' directives replace the 'proxy_set_header' ones in the venv doc?

Looking at the uwsgi doc, it seems they might do different things.

...

2. What document root(s) and alias(es) to use for Postorius and Hyperkitty and the Django admin on a server that also runs other services (e.g., Postfix for non-list mail and Roundcubemail)?

If you can separate Mailman from other services by subdomain

Alas, I can do that for all but one of the subdomains I have in production.

For the past 15 or so years, users of that subdomain have used mail.domain.tld for MM2, roundcubemail, and an admin web UI that manages regular mail.

The "/" has gone to roundcubemail, and users to go other directories for the other services. For example, MM2 users currently go to /mailman.

, you can

configure them separately and for Mailman, root is irrelevant as everything is proxied or aliased in a location directive. For example, Mailman on the server that supports this list uses the lists.mailman3.org domain and we have (excerpted)

server {
         listen 443 default_server;
         root /usr/share/nginx/html;
         index index.html index.htm;
# root and index are probably irrelevant as we never go there
         server_name lists.mailman3.org;
         ssl on;
#ssl stuff
         location / {
                 proxy_pass http://127.0.0.1:8000/;
# other proxy stuff

In this example, / goes to MM3.

The assumption here and in the MM3 docs is that we're standing up a dedicated server where MM3 pages should be served as the default. That's a totally valid design decision, and one could argue it's superior to running a bunch of other services on one machine.

It's not the situation I have to deal with, though. Short of changing a long-standing URL, what I'm looking to do is have "/" continue to default to roundcubemail, and have users type in longer URLs for MM3 and other services.

You're right that the root and index directives above are irrelevant since / goes to MM3 via proxy.

What I'm asking is what root(s) and location(s) to use with nginx where MM3 isn't the default.

Thanks again!

dn

        } location /static/ { alias /var/spool/mailman-web/static/; } location /robots.txt { alias /usr/share/nginx/html/robots.txt; } location /favicon.ico { alias /var/www/listorg/images/favicon.ico; } }

And for the other stuff we have

server { listen 443; server_name .list.org mirror.list.org mirror.mailman3.org; root /var/www/listorg; ssl on; # ssl stuff }