My domain is:
I ran this command:
sudo certbot certonly --webroot -w /home/adr/apps/opt/apache-htdocs -d adrhc.go.ro --preferred-challenges http --keep
It produced this output (ya, I know what this means, skip it please):
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for adrhc.go.ro
Using the webroot path /home/adr/apps/opt/apache-htdocs 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: go.ro
Please see the logfiles in /var/log/letsencrypt for more details.
My web server is (include version):
nginx 1.13.5
The operating system my web server runs on is (include version):
Ubuntu 16.04.3 LTS
My hosting provider, if applicable, is:
personal server
I can login to a root shell on my machine (yes or no, or I don’t know):
yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
no
This is in fact a larger problem besides not being allowed to get a certificate!
The adrhc.go.ro name is a sub domain of ISP’s domain: go.ro
I control the adrhc part of the name but not the go.ro part. I also own and control the computer pointed by adrhc.go.ro.
Now imagine that many subscribers like me to same ISP want a certificate from letsencrypt; at some point the limit is naturally reached for go.ro as already happened. But from my point of view and also the other hundred thousand of the same ISP’s subscribers the limit doesn’t make sense because depends on something I can’t control. Now the situation is strange: some few lucky ISP’s subscribers got the letsencrypt certificate while the more than vast majority can’t. What is the solution for this kind of situation?