On Tue, Jul 29, 2025 at 2:25 PM Willie Castillo < Willie.Castillo@caemilusa.com> wrote:
The issue started right after the site's CERT expired. The CERT expired on 7/8/25. This is what's in the log...
Jul 16 15:19:45 2025 (3777209) Connection to HyperKitty failed: HTTPSConnectionPool(host='XXX.com', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/urls?mlist=jmats-versions%40XXX.com (Caused by SSLError(SSLCertVerificatio nError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1000)')))
The CERT has been updated but the 7/25 message is not archived still.
While at it, also edit your /etc/mailman3/mailman-hyperkitty.cfg to what is documented so that the issue doesn't recur:
[general]
base_url: http://127.0.0.1:8000/archives/
api_key: Secret_Hyperkitty_API_Key
PS: I haven't seen your responses to @Mark Sapiro <mark@msapiro.net>'s questions quoted below:
Did the new post get archived? If so, why is last post at still July 25,
2025? If no, why not. The post must go to the archiver to cause the
queue to be processed.
If the post was archived and the July 25 messages are still queued,
what's in Mailman's mailman.log. There should be error messages and
tracebacks indicating the issue.
-- 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]