Could you try applying the patch from this pull request and see if that solves the problem? I believe you’re running into this issue because Let’s Encrypt started reusing existing valid authorizations a few months ago.
1 Like