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: https://heitara.de/
- I ran this command: $ sudo certbot renew --dry-run
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/heitara.de.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for kunert.pro
http-01 challenge for www.kunert.pro
http-01 challenge for heitara.com
http-01 challenge for heitara.de
http-01 challenge for www.heitara.com
http-01 challenge for www.heitara.de
Waiting for verification...
Challenge failed for domain kunert.pro
Challenge failed for domain www.kunert.pro
http-01 challenge for kunert.pro
http-01 challenge for www.kunert.pro
Cleaning up challenges
Attempting to renew cert (heitara.de) from /etc/letsencrypt/renewal/heitara.de.conf produced an unexpected error: Some challenges have failed.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/heitara.de/fullchain.pem (failure)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates below have not been saved.)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/heitara.de/fullchain.pem (failure)
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates above have not been saved.)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: kunert.pro
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for kunert.pro - check
that a DNS record exists for this domain; DNS problem: NXDOMAIN
looking up AAAA for kunert.pro - check that a DNS record exists for
this domain
Domain: www.kunert.pro
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for www.kunert.pro -
check that a DNS record exists for this domain; DNS problem:
NXDOMAIN looking up AAAA for www.kunert.pro - check that a DNS
record exists for this domain
- I ran this command: $ sudo certbot delete
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Which certificate(s) would you like to delete?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: heitara.de
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel):
- I ran this command: $ sudo ls /etc/apache2/sites-enabled/
It produced this output:
heitara.com.conf heitara.de.conf kunert.pro.conf
heitara.com-le-ssl.conf heitara.de-le-ssl.conf kunert.pro-le-ssl.conf
- I ran this command: $ sudo a2dissite /etc/apache2/sites-enabled/kunert.pro.conf
It produced this output:
ERROR: Site /etc/apache2/sites-enabled/kunert.pro does not exist!
- I ran this command: $ sudo a2dissite /etc/apache2/sites-enabled/kunert.pro-le-ssl.conf
It produced this output:
ERROR: Site /etc/apache2/sites-enabled/kunert.pro-le-ssl does not exist!
- I ran this command: $ apache2ctl -t
It produced this output:
AH00526: Syntax error on line 49 of /etc/apache2/sites-enabled/heitara.com-le-ssl.conf:
SSLCertificateFile: file '/etc/letsencrypt/live/heitara.de/fullchain.pem' does not exist or is empty
Action '-t' failed.
The Apache error log may have more information.
- I ran this command: $ sudo certbot delete --cert-name kunert.pro
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
No certificate found with name kunert.pro (expected /etc/letsencrypt/renewal/kunert.pro.conf).
- I ran this command: $ apache2ctl configtest
It produced this output:
AH00526: Syntax error on line 49 of /etc/apache2/sites-enabled/heitara.com-le-ssl.conf:
SSLCertificateFile: file '/etc/letsencrypt/live/heitara.de/fullchain.pem' does not exist or is empty
Action 'configtest' failed.
The Apache error log may have more information.
-
I ran this command: $ sudo systemctl restart apache2
It produced this output: (no output) -
I ran this command: sudo systemctl status apache2
It produced this output:
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor prese>
Active: active (running) since Tue 2022-02-15 10:47:46 CET; 57s ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 258441 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/>
Main PID: 258457 (apache2)
Tasks: 36 (limit: 36046)
Memory: 119.8M
CGroup: /system.slice/apache2.service
├─258457 /usr/sbin/apache2 -k start
├─258458 /usr/sbin/apache2 -k start
├─258459 /usr/sbin/apache2 -k start
├─258460 /usr/sbin/apache2 -k start
├─258461 /usr/sbin/apache2 -k start
├─258466 /usr/sbin/apache2 -k start
├─258483 /usr/sbin/apache2 -k start
└─258493 /usr/sbin/apache2 -k start
Feb 15 10:47:46 vmd54795.contaboserver.net systemd[1]: Starting The Apache HTTP>
Feb 15 10:47:46 vmd54795.contaboserver.net systemd[1]: Started The Apache HTTP >
lines 1-20/20 (END)
My web server is (include version): Apache/2.4.41 (Ubuntu)
The operating system my web server runs on is (include version): Ubuntu 20.04.3 LTS
My hosting provider, if applicable, is: https://contabo.com/, (VPS)
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 0.40.0
########################################################
Dear valued Let'sEncrypt community,
today I received an reminder by e-mail, that the awarded certificates of my webserver will expire on on 26 Feb 22 12:43, although the automatical renewal process has been setup.
The automatic certificate renewal has been running successfully and without problems since 2019.
Two websites have been running on the server so far. 1. 'heitara.de' and 2. 'kunert.pro'. Further a 301-redirect to 'heitara.de' has been set up for the domain heitara.com.
At the end of 2021 I canceled the domain contract for the domain 'kunert.pro', but without doing any changes at the server, e.g. removing the domain 'kunert.pro' from the virtual hosts. The domain expired silently.
The last system update followed by a restart of the server was carried out on January 21, 2022. Also without problems.
As of today I received the above mentioned email and ran the above listed commands to determine the cause of the error. The reminder e-mail contains the following domains:
[...]
'heitara.com'
'heitara.de'
'kunert.pro'
'www.heitara.com'
'www.heitara.de'
'www.kunert.pro'
[...]
I suspect that it has something to do with the canceled domain 'kunert.pro', but I can't find a corresponding solution in the forum.
My goal is to renew the certificate for the domain heitara.de. The domain 'kunert.pro' is no longer required and a certificate is not longer required.
Finally I ran the commands $ sudo a2dissite kunert.pro.conf && sudo a2dissite kunert.pro-le-ssl.conf. This finally worked for the first time.
I would be very grateful for any support in this matter. If you need any further informations or outputs of the system, please let me know.
Thank you in advance and best regards
Matthias
