2022-10-09 LetsEncrypt found a certificate signing request with a sha1 hash and rejected it
One of my oldest certificate signing request files was still using a sha1 hash and LetsEncrypt started rejecting it. As soon as I realized it used the old hash I redid it and wondered why it was still accepted in 2022. This also mean the private key of this service is showing age. Maybe time to regenerate it. The announcement is at Rejecting SHA-1 CSRs and validation using TLS 1.0 / 1.1 URLs - API Announcements - Let's Encrypt Community Support.