On Tue, Jan 04, 2022 at 11:13:54PM +0000, Mark Sapiro (@msapiro) wrote: > Mark Sapiro commented: > https://gitlab.com/mailman/mailman-suite/-/issues/22#note_801370201 > > I don't know what's responsible for the TLS request. What is your > setting for `MAILMAN_REST_API_URL`? if it is `https`, you might try > `http` instead
``` $ sudo grep REST_API_URL /etc/mailman3/mailman-web.py MAILMAN_REST_API_URL = 'http://localhost:8001' ``` And that `http` was there way before the network sniff was done. ( https://gitlab.com/mailman/mailman-suite/-/issues/22#note_801291946 ) > That said, issues with downstream packages should be reported to the > downstream packager, Debian in this case, rather than here. Done: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003157 And the Debian packagers are also recieving this email. > Then if the problem is upstream, the packager can come here. Current question: What causes the "Mailman REST API not available."? Is it mailman3-web not seeing the response to `GET 3.1/domains`? Or is it the '400 Bad request' in response to TLS request? Responses I hope to recieve are like * Enable extra logging of mailman-suite by ... * At path/to/django/settings/file somewhere line number ... you find foobar, comment that out to get .... and try again. Groeten Geert Stappers -- Silence is hard to parse
