#1003157 Mailman REST API not available. Please start Mailman core.

Package:
mailman3-web
Source:
mailman-suite
Submitter:
Geert Stappers
Date:
2022-06-24 16:21:05 UTC
Severity:
important
#1003157#5
Date:
2022-01-05 10:37:51 UTC
From:
To:
Package: mailman3-web
Version: 0+20180916-8
Severity: important
Justification: renders package unusable


Hello,


My installation of mailman3-web yields:

    Mailman REST API not available. Please start Mailman core.


Further information will be provided in follow-up email.
(This submit message is for getting a bugreportnumber.)


Groeten
Geert Stappers
#1003157#10
Date:
2022-01-05 11:50:30 UTC
From:
To:
```
$ 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 )
And the Debian packagers are also recieving this email.

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
#1003157#15
Date:
2022-06-24 16:04:44 UTC
From:
To:
With MAILMAN_REST_API_PASS without / and - character does it work.


Now closing the BR that I opened.