On Thu, Jun 6, 2024 at 11:51 AM Marcus Bautze via Mailman-users < mailman-users@mailman3.org> wrote:
Am 06.06.2024 um 10:42 schrieb Odhiambo Washington:
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 Keys are in mailman-hyperkitty.cfg and mailman-web.py and this are the same Keys.
I Think the error is produced from nginx :-/
the nginx.conf-file (/etc/nginx/plesk.conf.d/server.conf) says
(the [URL] ist lists.domain.tld, therefore the "lists*-section)
"server { listen [IP]:443 ssl; http2 on;
server_name lists.*; ssl_certificate /opt/psa/var/certificates/scfwTGe5L; ssl_certificate_key /opt/psa/var/certificates/scfwTGe5L; location / { proxy_pass https://[IP]:7081; proxy_hide_header upgrade; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For$proxy_add_x_forwarded_for; } }
I see your installation is not what I am used to so I have to take two steps backwards. And my competence with nginx is quite wanting :-)
-- 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]