On 1/23/22 07:41, Josef Dietl wrote:
The issue here is accessing the hyperkitty API. The base URL for these accesses is configured in mailman-hyperkitty.cfg. From what I see here, that is something like
http(s)://host.example.com/hyperkitty/If you appendapi/to that base URL and go there in a web browser do you get a page of documentation of the HyperKitty API? If so, then figure out why it works from a web browser and not when Mailman core does it. If you get the 403, figure out why. This is probably an nginx issue.Seems like an nginx issue indeed. However, I'm an apache guy, trying to re-educate myself on nginx. OK, here's the result of changing mailman-hyperkitty.cfg from
http(s)://host.example.com/hyperkitty/tohttp(s)://host.example.com/hyperkitty/api/
Do not make this change in mailman-hyperkitty.cfg. That will produce 404's for sure. This was only a suggestion to try from a browser.
Yes, if I open things from the web browser, I do get the HyperKitty API doc.
OK. That means you can access HyperKitty's API from a browser at
http(s)://host.example.com/hyperkitty/api/. This is the same thing
Mailman core is doing if base_url is set to
http(s)://host.example.com/hyperkitty/, so what's the difference
between Mailman core's access via mailman-hyperkitty and your's via the
web browser.
For further diagnosis, you might try wget -O- http(s)://host.example.com/hyperkitty/api/ on the Mailman server.
With what follows below, I guess it's a timeout: Processing a message takes longer than rendering a HTML document.
Jan 22 20:26:27 2022 (149435) ACCEPT: <AM0PR04MB4785365CA1BB735884E149CEC25C9@AM0PR04MB4785.eurprd04.prod.outlook.com> Jan 22 20:26:28 2022 (149439) HyperKitty failure on https://[FQDN]/hyperkitty/api/api/mailman/urls:
Do not include the api/ in base_url. That was just for testing with a web browser or wget/curl.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan