Mark Sapiro wrote:
Because those aren't the settings that matter for this. What if anything are your settings in the mailman.cfg [webservice] section for hostname: port: admin_user: admin_pass: use_https: (defaults in our distribution are localhost, 8001, restadmin, restpass and no respectively - I don't know if Debian changes these). These need to match the Django settings MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass'
They do match. Even the port (still on 8001).
The REST API is apparently not listening on the host/port this is trying to connest to.
Apparently. The question is why.
What is executing the manage.py command to start Django. Is it user list?
Probably. It depends on who is calling it. I understand too little of the new architecture. But mailman3.service is run as list, mailman3-web.service as root.
I don't use uwsgi and know little about it so I don't know what the Unix domain socket /run/mailman3-web/uwsgi.sock connection is for, but this appears to be some miscunfiguration between apache and uwsgi. Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via tcp port 8000 and uwsgi is configured with [uwsgi] uwsgi-socket = 0.0.0.0:8000
I too have no experience in the combination ow apache and uwsgi. The only other uwsgi app I'm running is on another server and running under nginx.