Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
It produced this output:
"Logged at" 2021-06-14. There are no recent certificates logged here for our domain. But we are hitting this issue:
"Error creating new order :: too many certificates already issued for: neo4j.io:" (from acme.sh)
We see this for both your staging and production environments. However we should be able to issue 30,000 certs using the staging environment - and we don't think we have done anything like that many. [2]
According to [2] we should be able to figure out which certs have been issued, and work back to find if we have a leak in our automation.
Hi Mike, I think we have actually done the request before. Been using Letsencrypt seamlessly since 2018.
I did not count them but there are a lot recently.
Where can I get a list of these. I suspect the issue is on our side, but cannot fathom where they are coming from. BTW does that limit apply to across staging/production?
I take it back - ARGH! I was not hallucinating but crt.sh is returning inconsistent results. Here is the same crt.sh url I used 5 minutes ago showing nothing since Jan 2021 and is what I saw originally. My url: https://crt.sh/?Identity=neo4j.io&deduplicate=Y
Thanks for all the info. My best guess then is that our automation is actually issuing production certificates, which is surprising since we are using the staging flag [1]
This would explain why both environments are failing, and why e2e type certs.
I have no explanation for this or your original question.
