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 ![]()