Problem with renewing multiple domains using simp_le

My domain is: Multiple domains (one example:

I ran this command: for file in /var/certs/; do (
currdate=$(date +"%d/%m-%y %T");
atrecord=$(dig +short @ ${file##
if [[ $atrecord =~ “IP1” ]] || [[ $atrecord =~ “IP2” ]]
wwwrecord=$(dig +short @ www.${file##/});
if [[ $wwwrecord =~ “IP1” ]] || [[ $wwwrecord =~ “IP2” ]]
cd /var/certs/${file##
–email EMAIL
–tos_sha256 SHAKEY
–default_root /var/www/webrootauth
-f key.pem -f fullchain.pem -f account_key.json -d ${file##/} -d www.${file##/} > /var/bmss/certlog.txt
if [[ $? == 0 ]]
echo "$currdate: created certs for ${file##/}"
if [[ $? == 2 ]]
echo "$currdate: error creating certs for ${file##
) done

/bin/systemctl reload nginx.service
/bin/systemctl status nginx.service

It produced this output: some outputs are: 2018-03-13 17:28:27,178:INFO:simp_le:1383: Certificates already exist and renewal is not necessary, exiting with status code 1. <-- These output works. But some outputs are:
2018-03-13 17:27:24,960:INFO:simp_le:1211: Generating new account key
2018-03-13 17:27:27,424:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1):
2018-03-13 17:27:27,717:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1):
2018-03-13 17:27:28,056:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1):
ACME server returned an error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new registration :: too many registrations for this IP: see
Probably those sites that can’t be renewed.

My web server is (include version): CentOS Linux 7 (Core) with Nginx

I checked the rate limit link ( to see if that’s the problem, and last update is yesterday, but I don’t know what have changed on rate limit that could cause this problem. I’ve lost more than 30-40 certs today and yesterday so I have no idea if it’s because of the changed rate limits or if it’s something else.

Thanks for taking your time to read this!

Hi @SantinoPetrovic,

Does simp_le not persist account registrations? It appears that you’re creating a new account for each certificate request, which is the reason for hitting the rate limit here.

Hi schoen, thanks for the reply!

This is pretty weird for me, because this script has been there for over a year without any problems until yesterday. Is there something new that have changed in Let’s Encrypt that could create this problem?

Do you share your infrastructure with someone else, like a shared hosting server?

Hi again,

It looks like it was a older client I’ve used (

I got help with setting up a newer one ( and it looks like it’s getting better.

Thanks for the help though!

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