there were too many requests of a given type letsencrypt

That could lead to undefined behaviour in the client and make it hard to debug the exact problem that has caused this. You confirmed on IRC that there were some manual modifications in etcletsencrypt (missing symlink). There Were Too Many Requests Of A Given Type Letsencrypt Manual Modifications In Since renewals are not automated, and in situations like this, barely functional, BETA is generous. If all goes well, youd end up with two directories in etcletsencryptlive and two different certificateskeys. I would suggest adding -keep-until-expiring as well so that your certificates are only renewed when theyre actually close to expiring (the client will just keep them as-is when theyre not). This will increase the rate limit for all domains included in that configuration, as theyre also included in the certificate. Lets Encrypt currently doesnt automatically add any cronjobs or other automation that might renew your certificate and fail in this way (this area is still very much a work in progress).

Theres no way the official client would have done so without user influence andor misconfigured cronjobs et cetera. I understand this is beta but I am drawing your attention to this because it is a huuuuuuge issue.

Note that this doesnt apply to subdomains: They all count towards the rate limit of your parent domain (TLD1).

That way, a new domain wont cause the rate limit for your existing domains to be increased.

There Were Too Many Requests Of A Given Type Letsencrypt Manual Modifications Inīoth will create a new certificate, which is the rate-limited operation (necessary to limit the OCSP signing load).

There were too many requests of a given type letsencrypt