DoS blocking Renewal

Issue is not the certificat itself, more the combination of software and router.

My domain is: desfos***.net
I ran this command: sudo snap run certbot renew --cert-name desfos***.net --dry-run -v
It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/desfos***.net.conf


Certificate not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator apache, Installer apache
Running pre-hook command: /etc/letsencrypt/renewal-hooks/pre/10-predeploy
Simulating renewal of an existing certificate for desfos***.net and 4 more
Performing the following challenges:
http-01 challenge for Identifier(typ=IdentifierType(dns), value='desfos***.net')
http-01 challenge for Identifier(typ=IdentifierType(dns), value='ha***.desfos***.net')
http-01 challenge for Identifier(typ=IdentifierType(dns), value='ne***.desfos***.net')
http-01 challenge for Identifier(typ=IdentifierType(dns), value='we***.desfos***.net')
http-01 challenge for Identifier(typ=IdentifierType(dns), value='www.desfos***.net')
Waiting for verification...
Challenge failed for domain ne***.desfos***.net
Challenge failed for domain www.desfos***.net
http-01 challenge for Identifier(typ=IdentifierType(dns), value='ne***.desfos***.net')
http-01 challenge for Identifier(typ=IdentifierType(dns), value='www.desfos***.net')

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Identifier: ne***.desfos***.net
Type: connection
Detail: During secondary validation: 216.58.xxx.xxx: Fetching http://ne***.desfos***.net/.well-known/acme-challenge/9YHPsJTq84u-JElhw0H7YfffP_N06f6DZaHW1wkpcZQ: Timeout during connect (likely firewall problem)

Identifier: www.desfos***.net
Type: connection
Detail: 216.58.xxx.xxx: Fetching http://www.desfos***.net/.well-known/acme-challenge/veWElOoxZrNhUA92ZwKH5eOYp-5tdmo_DqoodZ0vD4k: Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

Cleaning up challenges
Failed to renew certificate desfos***.net with error: Some challenges have failed.


All simulated renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/desfos***.net/fullchain.pem (failure)


1 renew failure(s), 0 parse failure(s)
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.

My web server is (include version): httpd-2.4.69-1.module_codeit.codeit.el9.aarch64
The operating system my web server runs on is (include version): Rocky Linux release 9.8 (Blue Onyx)
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): certbot 5.8.0

all righ, im not sure all those question are required BUT
when using the command above, im getting timeouts from verification randomly.
so being a little baffled, i decided to put on tcpdump on my router and on my server.
rand the dryrun, and comapred the tcpdump from both sides (thanks to chatGPT)
so a couple of SYN packet, hit my ROUTER that was not forwarded to my APACHE (7 packets for 2 different DNS entry so a total of 14 tcp packet droped by the router). i was like there is no way, firewall could not block a limitation or whatsoever...
this is when i disabled DoS and tried again.
output come as clearly no issue at all

(1:798)$ sudo snap run certbot renew --cert-name desfos***.net --dry-run -v
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/desfos***.net.conf


Certificate not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator apache, Installer apache
Running pre-hook command: /etc/letsencrypt/renewal-hooks/pre/10-predeploy
Simulating renewal of an existing certificate for desfos***.net and 4 more
Performing the following challenges:
http-01 challenge for Identifier(typ=IdentifierType(dns), value='desfos***.net')
http-01 challenge for Identifier(typ=IdentifierType(dns), value='ha***.desfos***.net')
http-01 challenge for Identifier(typ=IdentifierType(dns), value='ne***.desfos***.net')
http-01 challenge for Identifier(typ=IdentifierType(dns), value='we***.desfos***.net')
http-01 challenge for Identifier(typ=IdentifierType(dns), value='www.desfos***.net')
Waiting for verification...
Cleaning up challenges
Dry run: skipping deploy hook command: /etc/letsencrypt/renewal-hooks/deploy/10-homeassistant
Dry run: skipping deploy hook command: /etc/letsencrypt/renewal-hooks/deploy/20-router

so ... i have a bit of an issue here...

i will not disable DoS from the router. i am using a ASUS ROG AXE GT16000

is there a way to "slower/throttle the request" it might seems that certbot is sending too many request rapidly, might be due because i have like 5 hostname on the same CRT and now its it trapped as a DoS by the AsusRouter, it was not before i added 2 more.

so i need to disable DoS, do the renew, and enable DoS, which beast the automation process :wink:

Hi @crishna,

I find that is the mostly case.

yes it was DoS protection from the router. so i am asking, if its possible to throttle the request. so the router will not trap is as a DoS.

I do not believe so, but there are others far more knowledgable than me.

Also Let's Encrypt uses Multi-Perspective Validation Improves Domain Validation Security - Let's Encrypt
Thus you will see requests from multiple Geos for the secondary validation.

You shouldn't have to.
Just "teach" it that this is normal and expected.

No there isn't. As Bruce noted Let's Encrypt validates from (currently) 5 perspectives around the world. This will soon be 7 and further changes possible. See: Let's Encrypt is adding two additional remote perspectives for domain validation

A couple options

Use a DNS Challenge. Often DNS Servers are more tolerant of frequent requests. You didn't mention which you use but something to consider.

Use a pre-hook and post-hook to relax the DoS during the renew and restore it after. This exposes you for only very brief times during renew.

You could try a different Certificate Authority but all of them also do multi-perspective validation so I doubt that would help.

i did, ran that renew --cryrun 5 times... all got SOME timeout not all of them...
when i disabled DoS from the router, it worked at first run. --dryrun
it all points to there.
i just did tried again, now 3 are timing out (few minutes ago was only 2)

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Identifier: ha***.desfos***.net
Type: connection
Detail: During secondary validation: 216.58..: Fetching http://ha***.desfos***.net/.well-known/acme-challenge/EEXTEOmwNLK4PxY-ZP39bQewMcdwUolvUeWZx6JNGTM: Timeout during connect (likely firewall problem)

Identifier: ne***.desfos***.net
Type: connection
Detail: During secondary validation: 216.58..: Fetching http://ne***.desfos***.net/.well-known/acme-challenge/xPLOgMjBdTP7NvwjpaAzYrK-z8mtCxnzvVbCIQ9cwKY: Timeout during connect (likely firewall problem)

Identifier: www.desfos***.net
Type: connection
Detail: During secondary validation: 216.58..: Fetching http://www.desfos***.net/.well-known/acme-challenge/WqWPVkizKmyJ07hKghpHJxlfZYGbkV1ijdTi3YbvYtE: Timeout during connect (likely firewall problem)

and now if i disable DoS from router, all is good.

seems requeste are comming too fast and my asus router block it.

well im afraid i have no interface admin to configure DoS from the asus router OTHER than disable/enable :wink:

One other possible workaround is to validate each name individually.
Then validate them all at once.
[sounds like nothing will change]

You must understand that LE validations are usually cached [up to 30 days].
So, the same account trying to revalidate recently validated names will skip that process.

That's because it's a router [not a real firewall - LOL]

seems requests are coming too fast and my asus router block it [is TOO SLOW].

A good work-around in general for the situation. Just cautioning that the 30 day cache is being shortened. Will only be 7 HOURS in 2028. Still likely long enough for them to implement their own "pacing". Just wanted to note so they don't overly rely on that long duration.

We will also be reducing the authorization reuse period from 30 days to 10 days. In 2028, the reuse period will shrink to seven hours.

From: 64-Day Certificate Lifetimes Coming Feb 2027 - Let's Encrypt

@crishna We cross-posted earlier. Did you see other options like:

pre-hook, and post-hook.

used that to disable DoS before, make the renew and enable after.

tested and working fine now!

using ssh to send nvram command and restart service on the router. awsome! thanks Mike!