Renewals counting against weekly create limits

Please fill out the fields below so we can help you better.

My domain is: ifsight.net

I ran this command: sudo docker exec certbot /usr/certbot/venv/bin/certbot certonly --no-self-upgrade --non-interactive --agree-tos --standalone --preferred-challenges http-01 --email EMAIL@EMAIL.com -d dev.baltimorecity.ifsight.net,health.dev.baltimorecity.ifsight.net

It produced this output: There were too many requests of a given type :: Error creating new cert :: too many certificates already issued for: ifsight.net

My web server is (include version): unrelated as I concat the certs together, but haproxy 1.6

The operating system my web server runs on is (include version): docker centos6

My hosting provider, if applicable, is: self hosted aws

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

from https://crt.sh/?Identity=%.ifsight.net, it seems that my renewals are counting against new certs. My renewal/cron command is

sudo docker exec certbot /usr/certbot/venv/bin/certbot renew --preferred-challenges http-01 --no-self-upgrade --non-interactive --agree-tos

and you can also see by the timestamps it is done in the middle of the night for North America, so it is not anyone manually running these commands.

With all that being said, I am unable to make new certs. These clients are independent so I am not looking to flatten them all into one certificate to help reduce the number of certs.

Presently renewals must be done before new issuance. I understand that's difficult to arrange with independent clients.

Luckily this is already slated to change very soon. Please see this API announcement.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.