On Mar 19, 2021, at 4:53 PM, Jens Günther <jens.guenther@posteo.de> wrote:
Sure. It's not much, when I get it right, file was created by debian-package automatically (I only post the lines without #):
->/etc/mailman3/uwsgi.ini
[uwsgi] uwsgi-socket = /run/mailman3-web/uwsgi.sock enable-threads = true chdir = /usr/share/mailman3-web wsgi-file = wsgi.py master = true process = 2 threads = 2 uid = www-data gid = www-data plugins = python3 attach-daemon = python3 manage.py qcluster logto = /var/log/mailman3/web/mailman-web.log
I have no clue about where the “/mailman” is even coming from.
It is possible that uwsgi isn’t aware that it is serving the website at a subpath (“/mailman3”) instead of “/“, so the redirects don’t correctly take in to account the subpath. I see that the subpath is taken into account when there is a forward slash in the end and weird things happening when it isn’t.
Could be Apache not setting the “SCRIPT_NAME” var correctly always, but from the docs2 it seems to me that your configuration is correct. Maybe you can try setting the SCRIPT_NAME explicitly using uWSGIForceScriptName to “mailman3" and see if that helps?
Am 20.03.21 um 00:28 schrieb Abhilash Raj:
Can you also share your uwsgi configuration?
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/
-- thanks, Abhilash Raj (maxking)