On Thu, Jun 6, 2024 at 11:28 AM Marcus Bautze via Mailman-users < mailman-users@mailman3.org> wrote:
Hallo,
Am 27.05.2024 um 14:33 schrieb Mark Sapiro:
Enabling archivers is done in mailman.cfg similarly to
[archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfgThank you, archiver is now starting. Now there's another problem:
In mailman.log i'm finding:
"Jun 06 10:16:16 2024 (3556489) ACCEPT: <d3072553-2f52-4bd7-b14a-2701863812c7@***> Jun 06 10:16:17 2024 (3556492) HyperKitty failure on https://[URL]/mailman3/hyperkitty/api/mailman/urls: <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> <hr><center>nginx</center> </body> </html> (403)"
in mailman-hyperkitty.cfg there is:
base_url: https://[URL]/mailman3/hyperkitty/api/mailman/urls
The documentation says that mailman-hyperkitty.cfg should contain:
[general] base_url: https://[URL]/archives api_key: S0m3SecretArchiverAPIKey
In settings.py, you should have: MAILMAN_ARCHIVER_KEY = 'S0m3SecretArchiverAPIKey'
The KEY is quoted in settings.py,m but not in mailman-hyperkitty.cfg and it must be the same in both files.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]