On 7/22/21 11:41 AM, Sarah H wrote:
here is the full error message. Nginx proxies on http.
Thanks for the log. It is basically just confirming what we see with this.
the curl commands above result in.
...
(venv) [mailman@sysname sarah]$ curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive curl: (52) Empty reply from server
I am at a loss to understand why HyperKitty isn't responding. Are you able to access HyperKitty normally from a web browser?
Do you get a response from
curl http://127.0.0.1:8000/hyperkitty/
If so, what?
What you should get from
curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive
is
<html><title>Auth required</title><body>
<h1>Authorization Required</h1><p>Please check whether
the MAILMAN_ARCHIVER_KEY is provided by you and it is
correct.
</p></body></html>
You should get the same response as a web page if you go to https://example.com/hyperkitty/api/mailman/urls. Do you?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan