On 8/14/21 9:34 PM, Stephen J. Turnbull 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.
Not quite, but very soon.
pabsta@gmail.com writes:
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.
I'm sure that's right.
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 >
I see in the above upstream: "http://127.0.0.1:8006/accounts/login/",
but in your settings
ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https"
I suspect you may be getting a redirect from http to https which is losing POST data and you need to change
proxy_pass http://127.0.0.1:8006;in your nginx configuration to
proxy_pass https://127.0.0.1:8006;or set
ACCOUNT_DEFAULT_HTTP_PROTOCOL = "http"
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan