On 11/25/22 23:00, Jan Eden via Mailman-users wrote:
proxy_pass http://127.0.0.1:8000; → proxy_pass http://unix:/opt/mailman/mm/var/mailman.sock;
and received an error message (as expected):
Because that won't work. You can't http to a unix socket in that way.
Use
uwsgi_pass unix:/opt/mailman/mm/var/mailman.sock;
There are obviously a couple of places where the http-socket on port 8000 is referenced (e.g. mailman_web/settings/mailman.py, /opt/mailman/mm/hyperkitty.cfg). Is there an overview of the required changes when using a different (file) socket?
If you configure uwsgi with only a unix socket and no http-socket,
nothing will be listening on port 8000. Thus, you need to configure
those references to public facing URLs and let ngnix determine where to go.
e.g., for mailman-hyperkitty.cfg
[general]
base_url: http://example.com/archives/
and in settings.py
POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com'
to override the localhost:8000 reference in
mailman_web/settings/mailman.py.
Those two are the only ones. While you might be able to change the references to something like
http+unix://%2fopt%2fmailman%2fmm%2fvar%2fmailman.sock/...
that may not work, and it's simpler to let ngnix handle it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan