On Aug 14, 2021, at 9:34 PM, Stephen J. Turnbull <turnbull.stephen.fw@u.tsukuba.ac.jp> wrote:
I'm sorry, I'm in a "second vaccination" fog at the moment (mending but concentration lasts only about 10 minutes), so I'll answer what I know offhand since Abhilash is busy and Mark is probably offline for vacation by now. Perhaps later somebody can give a fuller answer.
pabsta@gmail.com writes:
In comparison to the walkthrough, I did two changes; First, I used different port numbers , as it would otherwise conflict with other services on the server.
Thank you for the very precise description. It's very helpful.
Second, I disabled the social accounts authentification mechanisms.
This should not be a problem since you disabled only the providers (I think the socialauth base module is required even if you don't use it.)
I am still running on sqllite, as I am still testing things (one task at a time).
This should be no problem.
Using my "superuser" credentials, I can log to the admin section in a fraction of a second.
If you mean the django admin page https://localhost:800something/admin, that doesn't involve any part of Mailman at all.
However, if logout and attempt to login from the postorius website, I get a « 502 bad gateway » error after roughly 30 seconds. The logs in Systemctl for gunicorn register a "DIGEST-MD5 common mech free" error message
I would guess this is also just a connection drop because it doesn't receive the expected response within timeout.
and the nginx error logs just show a connection drop:
2021/08/12 18:11:09 [error] 26026#26026: *31 upstream prematurely closed connbection while reading response header from upstream, client: [ip redacted], server: [domain redacted], request: "POST /accounts/login/ HTTP/2.0", upstream: "http://127.0.0.1:8006/accounts/login/", host: "[domain redacted]", referrer: "https://[domain redacted]/accounts/login/?next=/mailman3/lists/" a >
1- If I attempt to login with improper credentials, the services respond normally, and I get the expected red box with "invalid credentials" message on the postorius page. It is only when proper credentials are given that the connection fails.
The only thing I can think of is that having sucessfully logged in, Postorius can't find Mailman core to populate your user page. That would explain why an invalid login (which is entirely within Postorius and Django) proceeds as expected, but a valid login would fail so spectacularly.
This would be my guess too, although, it will show MailmanApiError in logs.
Do note that that gunicorn logs don’t have all the logs from exceptions raised in Postorius, for that, you want to file the location of the ‘postorius’ or ‘root’ logger in your settings.py (I couldn’t find that, it seems like you skipped those).
So, I’d expect some error or something in the logs if this isn’t the actual case.
-- thanks, Abhilash Raj (maxking)