Le 18995ième jour après Epoch, Stephen J. Turnbull écrivait:
According to Google Translate, this means "Secure connection failed", which seems to be a webserver problem, not a Mailman problem. Recent Firefox is very picky: it wants a proper certificate (although free certificates such as CertBot will do), and it won't accept SSL or TLS versions less than 1.2. Make sure that your webserver is properly configured to use TLS >= v1.2, and has a properly configured certificate.
Yep, and maybe I wasn't clear enough, but all other pages display correctly. It's only when I try to log-in (ie: POST request).
This suggests that you're seeing a variant on the "redirect from HTTP to HTTPS loses POST data" problem. The description of the problem is different and I have no idea what your configuration is, but if the advice (not the problem description) looks familiar the following post may be of help: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
Unfortunately, it seems no related as far as I understand this post.
More information about your webserver and Django configurations would be useful.
You're right :) ... The request path is as follow:
Firefox --> haproxy front --> nginx on mailman server --> mm3-web socket (unix:/run/mailman3-web/uwsgi.sock)
The nginx conf is close to the proposed one on the Debian package:
upstream list.my_dom.ain_mm3 { server unix:/run/mailman3-web/uwsgi.sock fail_timeout=600; }
server { listen 443 ssl; listen [::]:443 ssl;
server_name list.my_dom.ain; server_tokens off;
ssl_certificate /etc/letsencrypt/live/list.my_dom.ain/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/list.my_dom.ain/privkey.pem;
location / { uwsgi_pass list.my_dom.ain_mm3; include /etc/nginx/uwsgi_params; } ...
Django config is as installed by Debian mailman3-web package.
Thank you whatever for your help !