Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let’s Encrypt project and the non-profit
organization that develops Certbot? We’d like to send you email about EFF and
our work to encrypt the web, protect its users and defend digital rights.
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for linuxcompitech.dynamic-dns.net
Using the webroot path /srv/http/linuxcompitech.dynamic-dns.net for all unmatched domains.
Waiting for verification…
Cleaning up challenges
An unexpected error occurred:
There were too many requests of a given type :: Error creating new cert :: too many certificates already issued for exact set of domains: linuxcompitech.dynamic-dns.net
Please see the logfiles in /var/log/letsencrypt for more details.
Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
It looks like that I have to wait for 7 days till I get my certificate or have I a choice to make a reset?
I’m pretty confused now because you were first showing an error which you got with certbot --manual, and then a different error which you got with certbot --webroot. The reason for the two errors is also quite different—are you happy with --webroot and not interested in using --manual anymore?
In terms of the rate limit, you can bypass this rate limit if you can add an additional domain name for the certificate. Otherwise, you can issue one more certificate 7 days from the oldest certificate that’s triggered this rate limit, which will be starting around midnight UTC on Friday, June 23.
actually, I’m still a beginner with letsencrypt and I think to do that with --webroot it is easier to handle. I’ve added an additional domain name, thanks for the tip. What I noticed, firefox was saying the connection is not secure.
SSLProtocol all -SSLv3
SSLProxyProtocol all -SSLv3