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

23 Dec 2021


      On 12/10/21 4:48 PM, Mark Sapiro wrote:
...
On 12/10/21 3:22 PM, David Newman wrote:
...
On 12/10/21 12:57 PM, Mark Sapiro wrote:
...
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.
If you are using uwsgi and proxy_pass http://127.0.0.1:8000 is working
for you, then I'm satisfied that the docs are OK now and we don't need
to say anything about uwsgi_pass.
...
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.
I think you can set the document root to the roundcubemail root and then
set locations for the Mailman destinations as, e.g.
   location /mailman3/ {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
location /archives/ {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
location /accounts/ {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
location /admin/ {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
location /user-profile/ {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
I haven't tried anything like this, so I'm not sure it will work, but I
think so.
Update: The above worked fine until MM3 informed a list owner of pending
subscription requests, with a URL like this:
https://lists.example.com/mailman/admindb/listname
and that URL returned a 404 error.
Adding a stanza for 'location /mailman/' to the nginx config above
clears the 404 error, but Postorius returns "Page not found" with no
entry in the web or MM3 logs, and a 200 OK in the Nginx logs.
I think the URL is supposed to go to the list page in Postorius. How to
configure this so that list owners and moderators get a valid URL for
list management?
Thanks!
dn