Need account ID to submit at Rate Limit Adjustment Request

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., 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): Directadmin

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

Hi @brandon

if you have one domain and if

you use a control panel, there is no Rate Limit Adjustment Request required.

Changed rate limits are relevant if a company is a big hoster. Or if it is something like an university with a lot of subdomains.

Why do you think you need a Rate Limit Adjustment?



Got an error now.

Checking through certificate transparency, It appears you are creating a subdomain for each listing for your company, In this case it would be ideal to create a wildcard certificate which could cover *

Wildcard certificates are designed for this sort of use case.


  I have already done that. Infact if you check the URL

you can see I have applied
that. Refer this screen shots

But it is not helping much with it.

You don’t use wildcard certs as your message claims, You can verify this with chrome by clicking the padlock and clicking Certificate (valid)

I am assuming you have hit the 50 maximum certificate per domain per week limit. In this case you should wait for the rate limit to expire, then issue a wildcard which will cover all your subdomains.

What they meant was to issue one certificate for " and *" and use that for all your sites.

(Note that a certificate for * works for names like but not names with additional ‘levels’ like or This may or may not work for you.)

You have a certificate like that, but you’re also issuing many additional certificates for names like "* and", or ones without wildcards like " and".

(You also have some certificates from the cPanel CA, instead of Let’s Encrypt, issued a few months ago.)

You may be able to adjust things so that you need fewer certificates (or you might not).

My bad, I must have missed the part where he’s issuing certificates like *


  So I logged in to account in my directadmin panel

and then in SSL option I hit wildcard SSL and I got that earlier
said certificate there. What I am missing here so I can get the
things working for the domain like or

I have tried that but it won’t work with how can I get that working?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.