Issues setting SSL for my subdomains (Multitenant application)

Help
1

I am trying to setup my SSL using Certbot for my multitenant application. So I made the request a couple of times when the server was running and after stoping the server, I can't verify anymore.

here is my response:

root@50-116-42-20:/home/rank/rank_secondary_backend# sudo certbot certonly --manual --preferred-challenges dns -d *.rankafrica.site -d rankafrica.site -v
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Requesting a certificate for *.rankafrica.site and rankafrica.site
An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see Failed Validation Limit - Let's Encrypt
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

The question is do I have to wait 1 week before retrying the process? the service is highly needed
My main domain rankafrica.site works well It is the subdomains such as www.test.rankafrica.site that lack the SSL and I can't use them

My domain is:
rankafrica.site and *rankafrica.site

I ran this command:
sudo certbot certonly --manual --preferred-challenges dns -d *.rankafrica.site -d rankafrica.site

It produced this output:
An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see Failed Validation Limit - Let's Encrypt

My web server is (include version): linode

The operating system my web server runs on is (include version): ubuntu 22.04

My hosting provider, if applicable, is: linode

I can login to a root shell on my machine (yes or no, or I don't know): Yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no

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

2

Hi @darlington, and welcome to the LE community forum :slight_smile:

I see you are doing it via:

Do you understand what is required?
Have you checked that all authoritative nameservers have the required TXT record before proceeding?
Was there any other error message in prior runs?

3 Likes
3

You have to wait an hour which has already elapsed since you posted.

There is a "duplicate certificate" rate limit which can block you for a week but that is a different error message than you see. The messages are explained in more detail below

The link in your error points to a page that says

All issuance requests are subject to a Failed Validation limit of 5 failures per account, per hostname, per hour.

2 Likes
4

The wildcard cert you requested will not work with www.test.rankafrica.site

The wildcard part of the cert only covers that level. Not deeper levels. That is different than how wildcard DNS entries work.

So, a cert with *.rankafrica.site would work with names such as

test.rankafrica.site
any-other-name.rankafrica.site
www.rankafrica.site

Not related to above but your HTTP requests do not redirect to HTTPS. That is allowed but usually not what people want. You should ensure you want to allow HTTP access to your domain. If not, add a redirect from HTTP to HTTPS

4 Likes
5

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