[MM3-users] Re: admin/login/ cannot be accessed

I don't see anything special in mailman-web.log. When getting the Django login page with HTTP2:

[pid: 811818|app: 0|req: 6/6] <mysite_ip_address> () {50 vars in 941 bytes} [Sat Dec 14 12:25:33 2019] GET /admin/login/ => generated 1806 bytes in 15 msecs (HTTP/2.0 200) 8 headers in 434 bytes (1 switches on core 1)

When getting the Django login page without HTTP2:

[pid: 811818|app: 0|req: 7/7] <mysite_ip_address> () {54 vars in 1001 bytes} [Sat Dec 14 12:31:40 2019] GET /admin/login/ => generated 1806 bytes in 16 msecs (HTTP/1.1 200) 8 headers in 434 bytes (1 switches on core 0)

Nothing is logged with/without HTTP2 when I try to enter the admin account credentials and hit "Log in", which is coherent with my previous post about tcpdump. As if nginx did not send the credentials to uwsgi. This makes no sense.

The following is the contents of /etc/nginx/uwsgi_params which is included in the server block;

uwsgi_param  QUERY_STRING       $query_string;
uwsgi_param  REQUEST_METHOD     $request_method;
uwsgi_param  CONTENT_TYPE       $content_type;
uwsgi_param  CONTENT_LENGTH     $content_length;

uwsgi_param  REQUEST_URI        $request_uri;
uwsgi_param  PATH_INFO          $document_uri;
uwsgi_param  DOCUMENT_ROOT      $document_root;
uwsgi_param  SERVER_PROTOCOL    $server_protocol;
uwsgi_param  REQUEST_SCHEME     $scheme;
uwsgi_param  HTTPS              $https if_not_empty;

uwsgi_param  REMOTE_ADDR        $remote_addr;
uwsgi_param  REMOTE_PORT        $remote_port;
uwsgi_param  SERVER_PORT        $server_port;
uwsgi_param  SERVER_NAME        $server_name;

Is there something incompatible here?