I’m using certbot certonly --webroot. I have thousands of domains to secure. It equates to roughly 100 SSL SAN certs to generate. While getting my process working, I used CTRL + C to cancel the certbot command a couple times. This left hanging requests, so now I get this error:
“Error creating new authz :: Too many currently pending authorizations”
A little research shows this might last as long as a week? It’s already been several days. To get around this issue, I’m considering using a new LE account. I’m considering doing something like this guy:
mv /etc/letsencrypt/accounts /etc/letsencrypt/accounts.off
and then provide a new account… Is there any issue with this? Keep in mind that certbot is NOT managing the certs after creating them - I have automated node.js scripts which take the certs when certbot is done, moves them into new directory structure, and manages and renews them there. This is because I need to use my own private key, which forced me to provide my own CSR, which causes certbot to NOT manage certs itself - it just outputs certs into the current working directory so my node scripts move the from there.
Anyhow, so that’s my setup, and I’m just wondering if I’m safe to switch between two accounts to temporarily get around this new authz 300 limit??