Hi Eggert,

thank you for your input. Unfortunately that did not work. After changing the line

ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ to ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/

and restarted apache2, still a similar behavior when accessing https://my.mailinglistserver.local/mailman/postorius/lists/

Page not found (404) Request Method: GET Request URL: https://mmy.mailinglistserver.local/mailma//postorius/lists/

What i find strange is that the URL is mangled. The 'n' from mailman is missing and now there is a second slash.

This all must happen inside the uwsgi-container as my request is modified.

Not Found: /mailma// [pid: 1346851|app: 0|req: 28/28] 10.254.253.13 () {52 vars in 827 bytes} [Mon Oct 25 17:47:21 2021] HEAD /mailman/ => generated 2773 bytes in 4 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core 1)

Am Mo., 25. Okt. 2021 um 17:19 Uhr schrieb Eggert Ehmke via Mailman-users < mailman-users@mailman3.org>:

Hello Stefan,

I had the same problem. While I did not find the reason for this strange behavior, I found a workaround. I changed the lines in the apache vhost file like this:

<IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule>

Note I only changed the single ProxyPass line from mailman3 to mailman. The url to access the web gui also changes like this:

https://my.mailinglistserver.local/mailman/postorius/lists/

This works for me, tell us your success. Would be nice when the problem could be solved finally, this happened to a few people.

Cheers, Eggert

...

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)

After enabling Debug, i see in the browser the following:

Page not found (404) Request Method: GET Request URL: https://my.mailinglistserver.local/mailman//postorius/lists/

Using the URLconf defined in urls, Django tried these URL patterns, in

Am Montag, 25. Oktober 2021, 10:45:50 CEST schrieb Stefan Bauer: this

...

order:

^$
^postorius/
^hyperkitty/
^user-profile/delete$ [name='mm_user_account_delete']
^user-profile/$ [name='mm_user_profile']
^accounts/
^admin/

The current path, /postorius/lists/, didn't match any of these.

You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page.

My apache configuration is very simply:

# more /etc/apache2/conf-enabled/mailman3.conf Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static

<Directory "/var/lib/mailman3/web/static"> Require all granted </Directory>

<IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule>

I dont see where the path gets traversed in the wrong way. Any help is greatly appreciated.

thank you.

Stefan

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

To comment my own text, as my typo let it look rude. I meant: I solved it by myself, just by thinking about it for a while again.

Stefan

Am Mo., 25. Okt. 2021 um 18:06 Uhr schrieb Stefan Bauer <cubewerk@gmail.com

:

So i fixed it by myself, just think about it again. ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/

Note the trailing slash at the end. After removing it, the webinterface is up again. But i have no idea, why this is NOW a problem and was not in the past. Maybe something has changed in the way, apache is handling this now.

Anyway, problem solved for me.

Am Mo., 25. Okt. 2021 um 10:45 Uhr schrieb Stefan Bauer < cubewerk@gmail.com>:

...

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)

After enabling Debug, i see in the browser the following:

Page not found (404) Request Method: GET Request URL: https://my.mailinglistserver.local/mailman//postorius/lists/

Using the URLconf defined in urls, Django tried these URL patterns, in this order:

^$
^postorius/
^hyperkitty/
^user-profile/delete$ [name='mm_user_account_delete']
^user-profile/$ [name='mm_user_profile']
^accounts/
^admin/

The current path, /postorius/lists/, didn't match any of these.

You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page.

My apache configuration is very simply:

# more /etc/apache2/conf-enabled/mailman3.conf Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static

<Directory "/var/lib/mailman3/web/static"> Require all granted </Directory>

<IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule>

I dont see where the path gets traversed in the wrong way. Any help is greatly appreciated.

thank you.

Stefan

Eggert Ehmke via Mailman-users writes:

This makes it even stranger. Removing the trailing / did not help in my case, but replacing the mailman3 for mailman in the ProxyPass line did.

Would be really nice to solve this problem at the root.

While I can't deny it's possible there's a Mailman bug, this sure looks like a uswgi issue. As far as I know, none of the active Mailman developers have ever used it, except maybe in a test installation to help solve a user problem. Someone who uses uswgi in production with Mailman is the obvious person to talk to the uswgi maintainers and to us.