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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is: Heroku
I can login to a root shell on my machine (yes or no, or I don't know): idk
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
I published a React website on Heroku and I linked it with the domain : www.blackflakes.com
But I encountered a problem when I tried to get an SSL certificate by using Heroku ACM.
The process failed.
Since I can access the website by using my domain, I deduced that the configuration with my DNS provider (OVH) is good.
Into their documentation, Heroku mentions that, if the problem isn't due to the DNS configuration, the rate limit set by Let's Encrypt can caused this issue.
I checked the certificate issuance history of the domain here: crt.sh | blackflakes.com
As you can see, since yesterday 14 certificates have been issued.
As I had a lot of problems with Heroku and my DNS provider I did many interactions on the Heroku dashboard so it's certainly because of that.
My questions are the following:
- May the rate limit set by Let's Encrypt be responsible for the "failed" output from Heroku?
- How long is the period to wait before be again able to generate a new certificate?
- Is the domain blacklisted / blocklisted by Let's Encrypt?
- Is it possible to deblock the situation?
Thanks by advance for your help.