letsencrypt rate limiting
cz8s opened this issue · comments
when building staging, we get followin error:
There were too many requests of a given type :: Error creating new cert :: Too many certificates already issued for exact set of domains: api.staging.pixelated-project.org,nicknym.staging.pixelated-project.org,pixelated.staging.pixelated-project.org,staging.pixelated-project.org
Please see the logfiles in /var/log/letsencrypt for more details.
@tuliocasagrande knows how to solve this.
@tuliocasagrande are you working on this ?
We kind of solved this problem when we created a persistent /storage partition and saved the /etc/letsencrypt folder inside of it.
However, before we could store a single letsencrypt certificate, we already had reached the limit. [1]
So we need to wait until we get an available slot and we're not going to lose those certificates this time.
[1] https://community.letsencrypt.org/t/rate-limits-for-lets-encrypt/6769
there's a dirty, hacky workaround for this: if you add another subject alt name like foo.staging.pixelated-project.org, you can mitigate the rate-limit ;)
I did this once playing with letsencrypt and running into the rate limit so you could give it try.
We successfully generated new certificates and saved them in /storage partition. 🎉 🎉 🎉