I hit the rate limit today. By googling, I found this thread, where @cool110 suggesting using the staging environment for testing.
Ah, good to know! But I wish I’d known about that before I got locked out of LE for a week.
I’d like to have gotten a warning in the certonly output the first four times. Something like: You have used 3 of 5 issues of example.com. Use --staging for testing.
Having RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset sounds like a good idea. @jsha
If it gets implemented, I’d suggest to use the seconds until it’s reset in RateLimit-Reset instead of the timestamp when it gets reset. This ensures it works on all systems, regardless of the time thrift which may exist.
$ letsencrypt certonly --staging
You have an existing certificate that contains exactly the same domains you requested and isn't close to expiry.
(ref: /home/keith/.config/letsencrypt/renewal/keithirwin.us.conf)
What would you like to do?
-------------------------------------------------------------------------------
1: Keep the existing certificate for now
2: Renew & replace the cert (limit ~5 per 7 days)
-------------------------------------------------------------------------------
Select the appropriate number [1-2] then [enter] (press 'c' to cancel):
@keith7, that message was there before, but appears only when you request a cert for exactly the same names as an existing cert on your system; the rate limit message is describing the overall limit and not measuring how many issuances you have left.