Hello everyone, I'm running gitlab on my server which is integrated with letsencrypt. For the past three weeks, one time per week, my server attempted to generate an SSL and filed with the following error :
letsencrypt_certificate (letsencrypt::http_authorization line 6) had an error: Acme::Client::Error::RateLimited: acme_certificate[staging] (letsencrypt::http_authorization line 43) had an error: Acme::Client::Error::RateLimited: Service busy; retry later.
When I noticed about two hours ago, I've tried about 6 times over these last two hours and am getting the same error. I have no idea what to do and would appreciate any help you can provide.
Do you have other cert requests coming from that same IP address? Because that sort of looks like you are hitting this rate limit: Rate Limits - Let's Encrypt
One way this can happen is if you have an ACME Client that goes into tight retry loop after experiencing an error. If so, that's two problems. One is the misbehaving ACME Client and whatever the original problem was.
That error message includes [staging]. Are you using the Let's Encrypt Staging system when this happens. Do you always?
More info would be helpful. The more answers to the questions on the form you should have been shown is a good start. Thanks
============================================
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Thank you for the prompt reply. No other certs are coming from this IP address but I don't know how gitlab handles this failure and I don't know how to test/get any feedback at all on what is going on...from gitlab or from you guys. Their community support is pretty weak unfortunately so I think I'm basically on my own. I know it is setup to renew once a week and was working fine for over a year and stopped mid December for some reason. In regards to the staging message, I don't know what that is referring to specifically. I have gitlab configured to not use letsencrypt's staging server but that might not be working or, it is, and that staging text refers to something else.
I am not comfortable giving out my domain.
The error provided is created whenever gitlab tries to request a certificate.
My web server is running Debian
Self managed/colocation hosting provider that is very small