The certificate chain has an expired certificate, which doesn't stop modern browsers from connecting, but depending on the particular configuration of the server/tool doing the checking, an invalid chain might trip it up.
https://www.ssllabs.com/ssltest/analyze.html?d=sa%2dupdate.space%2dpro.be&s=176.28.55.20&hideResults=on&latest It was https:// last time it was working, but depending on what the problem was or what fixed it, perhaps the chain got reverted somehow. On Fri, Jun 28, 2024, at 09:04, Bill Cole wrote: > Does anyone have time to figure out what's going on here? > > I alerted Rene to the problem and he fixed something on his machine, > which *is* now answering, however the check script is still saying it is > down. > > > Forwarded message: > >> From: [email protected] >> To: [email protected] >> Subject: checkSAupdateMirrors.sh on sa-vm.apache.org - 1 mirror DOWN, >> 0 mirrors STALE >> Date: Fri, 28 Jun 2024 12:18:26 +0000 (UTC) >> >> http://sa-update.dnswl.org/ (116.203.4.105): UP (CURRENT) >> >> https://www.sa-update.pccc.com/ (69.171.29.42): UP (CURRENT) >> >> ** https://sa-update.space-pro.be/ (176.28.55.20): DOWN >> >> http://sa-update.ena.com/ (96.4.1.5): UP (CURRENT) >> >> http://sa-update.ena.com/ (96.5.1.5): UP (CURRENT) >> >> http://sa-update.verein-clean.net/ (5.161.203.54): UP (CURRENT) >> >> http://sa-update.verein-clean.net/ (128.140.71.96): UP (CURRENT) >> >> https://sa-update-asf.snb.it/ (151.80.178.91): UP (CURRENT) >> >> http://sa-update.spamassassin.org/ (64.142.56.146): UP (CURRENT) > Attachments: > * signature.asc
