On 10/25/21 1:45 AM, Stefan Bauer wrote:
Dear Users,
I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the web-interface via
https://my.mailinglistserver.local/mailman3/postorius/lists/
I receive
Not Found: /mailman//postorius/lists/ [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core 1)
Where does the wrong path come from (mailman vs. mailman3)
See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U...
...
<IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule>
Others have found that removing the trailing slash from
ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/
to make it
ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost
fixes the issue.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan