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

12 Dec 2019

Django version is 2.2.6-1ubuntu1
Disabling HTTP2 in nginx means disabling it for all server blocks
listening on the same IP, which would degrade all other servers.
Doing so leads to another error:
This page isn’t working
<mysite> didn’t send any data.
ERR_EMPTY_RESPONSE
I cannot run nginx and apache on the same <ip_address>:443 port either.

I found no error in mailman3 or syslog logs.
In /etc/mailman3/mailman.cfg, I have:
[logging.debian]
format: %(asctime)s (%(process)d) %(message)s
datefmt: %b %d %H:%M:%S %Y
propagate: no
level: debug
path: mailman.log

Yet, mailman.log does not seem to show debug level information.
On Wed, Dec 11, 2019 at 7:04 PM Abhilash Raj <maxking@asynchronous.in>
wrote:
...
On Wed, Dec 11, 2019, at 9:25 AM, jean-christophe manciot wrote:
...
Ubuntu 20.04
python3-django 2:2.2.6-1ubuntu1
python3-django-hyperkitty 1.3.1 (built from sources)
mailman3-full 3.2.2-1
Which version of Django are you using?
...
Nginx server configuration:
...
      ########
        # Static
      ########
        location /favicon.ico
        {
                alias &lt;mysite_dir>/static/hyperkitty/img/favicon.ico;
        }
        location /static/favicon.ico
        {
                alias &lt;mysite_dir>/static/postorius/img/favicon.ico;
        }
        location /static/
        {
                alias &lt;mysite_dir>/static/;
        }

      #######################
        # Upstream uwsgi server
      #######################
        location /
        {
                include /etc/nginx/uwsgi_params;
                uwsgi_pass 127.0.0.1:&lt;uwsgi_server_port>;
        }
...

where:

<mysite_dir> is a symlink to <django_dir>/static
<uwsgi_server_port> matches the one defined in

/etc/mailman3/uwsgi.ini:
...
[uwsgi]
# Port on which uwsgi will be listening.
uwsgi-socket = 127.0.0.1:&lt;uwsgi_server_port>

The config looks good to me in a quick glance.
...
All 3 systemd services run fine:

mailman3
mailman3-web
qcluster

I'm trying to login to the django administration pages.
I get the django administration login page at:
https://mysite/admin/login/
Logging in with the admin credentials leads to:
This site can’t be reached
The webpage at https://mysite/admin/login/ might be temporarily down or
it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR

This is very strange because it is the URL which I used to get the
login page in the first place.
Looking at the error, it seems like something somewhere is re-directing to
HTTP/2 or the request is based off of HTTP/2 and all the components in the
stack don't support HTTP/2, leading to the error message.
I haven't played a lot with HTTP/2 yet so I am not sure which specific
component in the stack could be incompatible here.
...
If I launch a test web server at another port with:
&lt;django_dir># python3 manage.py runserver &lt;mysite_ip_address>:8080
Performing system checks...

System check identified no issues (0 silenced).
December 11, 2019 - 17:50:48
Django version 2.2.6, using settings 'settings'
Starting development server at http://&lt;mysite_ip_address>:8080/
Quit the server with CONTROL-C.

and access it at http://&lt;mysite_ip_address>:8080/admin/login/ to
login with the same credentials as before, I get through and all the
django administration lines appear, although in a degraded layout:
Site administration
Accounts
Email addresses       Add     Change
Authentication and Authorization
Groups        Add     Change
Users Add     Change
Django Mailman 3
Mail domains  Add     Change
Profiles      Add     Change
...

Any idea what could be happening here?
Degraded layout is due to missing static files since the development
server that you spun off doesn't serve static files. So, that is okay.
...

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)
--
Jean-Christophe