Automatic renewal fails

Help
1

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: "paritsu.kenyoh.com"

I ran this command: "sudo certbot renew --dry-run"

It produced this output:


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/kenyoh.com.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Simulating renewal of an existing certificate for kenyoh.com and paritsu.kenyoh.com

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
  Domain: kenyoh.com
  Type:   connection
  Detail: 178.198.86.104: Fetching http://kenyoh.com/.well-known/acme-challenge/L2PxQakVkB3DD1v4cAFmEkwG83TNoOV-HPEsApfwnVY: 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.

Failed to renew certificate kenyoh.com with error: Some challenges have failed.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
All simulated renewals failed. The following certificates could not be renewed:
  /etc/letsencrypt/live/kenyoh.com/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): "Apache/2.4.57 (Debian)"

The operating system my web server runs on is (include version): "Debian 12", "bookworm"

My hosting provider, if applicable, is:

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.1.0"

Automatic renewal is due (expiring in 28 days). Does not work. Test with "Let's debug" returns no issues. Disabling ufw does not resolve.

Any help would be greatly appreciated.

thx

2

Your paritsu subdomain passes Let's Debug but the error is for kenyoh.com which failed Let's Debug same as the renewal. They have two different IP addresses.

3 Likes
3

renew [without specifying a cert or domain name] will try to renew all the certs.

What shows?:
certbot certificates

1 Like
4 
sudo certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
  Certificate Name: kenyoh.com
    Serial Number: 32a92436820846190d01522a6c7e90ca3af
    Key Type: RSA
    Domains: kenyoh.com paritsu.kenyoh.com
    Expiry Date: 2023-12-10 15:53:23+00:00 (VALID: 28 days)
    Certificate Path: /etc/letsencrypt/live/kenyoh.com/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/kenyoh.com/privkey.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
5

This is key here. As kenyoh.com is down entirely, that IP address is probably not correct.

6

Can this be solved by forwarding "kenyoh.com" to "paritsu.kenyoh.com" at the registrar?

7

I am not sure what you mean by "forward" but you should just set the A record for kenyoh.com to the same address as for paritsu.

If you want, you could CNAME the paritsu subdomain to kenyoh.com so there is only one place to update the IP address. But, that is not required. You cannot CNAME kenyoh root name to paritsu subdomain as that is not allowed by DNS rules.

3 Likes
8

Thank you guys @MikeMcQ, @rg305 and @Osiris for posting. I appreciate.

As not being very familiar with DNS, it was probably by myself having screwed it up by "simplifying" domain config and DNS-records by earlier activities without recognizing creating troubles.
After having set the A record for "kenyoh.com" as suggested by @MikeMcQ and updated the ddclient config, the most recent scheduled attempt to automatically renew the certificate was successfull.

Actually all runing as expected.

thx again.

3 Likes
9

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