Eventually, I got it to work as I had to wait for the letsencrypt restriction. If letsencrypt is going to just use publicsuffix from golang/net, there will be problem. asked by henrik41 Talented edited by henrik41. Once a project has enabled a custom domain, in the ssl certificates tab, there would be more than one option: Use your own certificate, or request a certificate.
Plugins selected: Authenticator apache, Installer NoneĪttempting to renew cert () from /etc/letsencrypt/renewal/ produced an unexpected error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see. There were too many requests of a given type.letsencrypt. I am wondering if this means that I will never be able to get a new cert ever? I do not know why it would put a rate limit do my domain, I mean I already have a certificate authorization from them. We have to wait for publicsuffix to merge that. The pull request has been recently updated according to publicsuffix requests.
There seems to be some progress in the discussion. So getting the certs works, it seems that LE does not want to issue real renew for mew :( weppos and other publicsuffix contributors there was discussing 'what's the best way to proceed given the large amount of requests'. So now I tried to renew my cert and I am getting this error.
There were too many requests of a given type letsencrypt code#
I was able to finally get a LE certs some months ago, it was all working. If you see Error creating new order: acme: error code 429 urn:ietf:params:acme:error:rateLimited or Error creating new order :: too many failed authorizations. I learned the rate limits issue back when I started using dyn dns service. Error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many failed authorizations.
0 kommentar(er)
