Let’s Encrypt error 429: Rate limit because VESTA doing "v-add-letsencrypt-domain" in loop to deleted domains

[vesta_sudo]

Hi!!

I have been using VESTACP for about 3 years, and I am really happy with it. But since 1 week ago I have an issue with SSL:

I can't add SSL to new domains added to VESTACP. It gives me:

Error: Let’s Encrypt new auth status 429 -> Which is that I have reached the limit at Let's Encrypt, because of so many errors in less than 3 hours (the others option are not suitable, because I am far away from having 100 domains with the same certificate)

So, I have been looking at the error logs from VESTACP (/var/log/vesta/error.log) where I have an infinite loop that every 5 minutes it tries to do the following:

Code: Select all

v-add-letsencrypt-domain  'user' 'domain.com' '' 'yes' 'yes' [Error 3] 

Where "user" exists but "domain.com" is a deleted domain. It does this to 4 unexisting domains (one of them was an alias of a deleted domain)

Anyone knows how to stop this infinite loop of VESTACP trying to add ssl to a deleted domain?

I have:

vesta 0.9.8
Ubuntu 18.04 (64 Bit)

Thanks in advanced!!

[vesta_sudo]

Solved it.

It was a rate limit of max 3 errors in 1 hour with Let's Encrypt.

To fix the issue, I edited

Code: Select all

/usr/local/vesta/bin/v-add-letsencrypt-domain

Found this line:

Code: Select all

well_known="$HOMEDIR/$user/web/$domain/public_html/.well-known"

And changed to:

Code: Select all

well_known="$HOMEDIR/$user/web/$rdomain/public_html/.well-known"

(I changed $domain to rdomain)

Also, in CloudFlare, I disabled:

"force HTTPS"

And in the SSL tab, I changed from "FULL" to "Flexible"

Everything OK now :)

-------------------------------------------

Some people said that typing:

Code: Select all

sudo apt-get install --reinstall vesta

Also helped with the same issue. When you reinstall VestaCP no data is lost. I didn't reinstall it, but could help if my solution doesn't work for you.

[Lucario76]

To solve the problem you must make sure that the domain has been completely removed from the server and then edit the following file:

Code: Select all

/usr/local/vesta/data/queue/letsencrypt.pipe

Then there will surely be the script that produces the problem, delete it and it will no longer try to generate the certificate.