Closed nitmir closed 8 years ago
Note that no certificates seems to be send to Certificate Transparency https://crt.sh/?q=hostnames-a-m.crans.org so it may not be related to #1561.
I get the same error using the last (4.1) letsencrypt-auto:
samir@bakdaur $ sudo /usr/scripts/src/letsencrypt/letsencrypt-auto --config /etc/letsencrypt/conf.d/hostnames-a-m.crans.org.ini certonly
[…]
Checking for new version...
Creating virtual environment...
Installing Python packages...
Installation succeeded.
Requesting root privileges to run letsencrypt...
/root/.local/share/letsencrypt/bin/letsencrypt --config /etc/letsencrypt/conf.d/hostnames-a-m.crans.org.ini certonly
You have an existing certificate that contains exactly the same domains you requested and isn't close to expiry.
(ref: /etc/letsencrypt/renewal/hostnames-a-m.crans.org.conf)
What would you like to do?
-------------------------------------------------------------------------------
1: Keep the existing certificate for now
2: Renew & replace the cert (limit ~5 per 7 days)
-------------------------------------------------------------------------------
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
An unexpected error occurred:
The server experienced an internal error :: Error creating new cert
Please see the logfiles in /var/log/letsencrypt for more details.
Note that no certificates seems to be send to Certificate Transparency https://crt.sh/?q=hostnames-a-m.crans.org so it may not be related to #/1561.
It's possible that it's the same root cause - hitting timeouts due to increased latency - but manifesting in different ways.
The timeout increase has been pushed to production - please test again.
Now I have There were too many requests of a given type :: Error creating new cert :: Too many certificates already issued for: crans.org
thus no certs were successfully retrieved since a month…
Only successfully issued certs should count in the rate-limt.
Hi all,
@schoen directed me here - I filed #2621 which may be a duplicate of this issue.
At the moment I can get certs on neither the --test
mode nor the production mode. So I believe that either this issue is not fixed, or that #2621 is a separate issue. I'm hopeful that I can help debug this.
Note that is https://github.com/letsencrypt/letsencrypt/issues/2621 (different repo).
I guess I'm unlikely to be able to debug this. For now, I can report that my problem still exists. Let me know when to test again.
I try to generate the certificate using crans.fr
which is a DNAME of crans.org
and it works. So this issue is resolved to me.
Hi
I try to generate a cert with a lot of SAN (~83). I use this config file:
I use the letsencrypt client version 4.0 from the debian jessie-backports. Staging work just fine :
However, I am unable to get a certificate from the production boulder:
here the content of
/var/log/letsencrypt/letsencrypt.log
Could someone have a clue of what the problem is ?