Starting around 2017-06-12 15:44 PDT Let’s Encrypt started consistently returning the following error: generic::internal: unable to fetch cert: 500 urn:acme:error:serverInternal: Error creating new cert
on one of our accounts (https://acme-v01.api.letsencrypt.org/acme/reg/8551380).
Our calling pattern did not change around that timeframe and as far as I could tell we shouldn’t be able to trigger this error code anyway as it signifies an issue with Let’s Encrypt infrastructure.
Can you look into this? If you need more details I’ll be happy to provide them in private.
Thanks a lot for taking a look! I appreciate that.
Let me know if you’d like me to share more details about our use case if that would help with the mitigation.