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.
It produced this output: Error while running apache2ctl configtest.
Action 'configtest' failed.
The Apache error log may have more information.
AH00526: Syntax error on line 8 of /etc/apache2/sites-enabled/ares.crucis.net-le-ssl.conf:
SSLCertificateFile: file '/etc/letsencrypt/live/ares.crucis.net-0001/fullchain.pem' does not exist or is empty
My web server is (include version): Apache/2.4.57 (Ubuntu)
The operating system my web server runs on is (include version): Ubuntu 23.10
My hosting provider, if applicable, is: self
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 2.1.0
I was trying to reinstall the certificates and somehow messed everything up. Now, getting certbot errors.
Error while running apache2ctl configtest.
Action 'configtest' failed.
The Apache error log may have more information.
AH00526: Syntax error on line 8 of /etc/apache2/sites-enabled/ares.crucis.net-le-ssl.conf:
SSLCertificateFile: file '/etc/letsencrypt/live/ares.crucis.net-0001/fullchain.pem' does not exist or is empty
You may have to disable that site to get Apache to start.
Once started, you can then move towards reinstalling the cert [if it still exists] OR reissuing a new cert and installing the new one.
Here's the result of "sudo apachectl -t -D DUMP_VHOSTS
VirtualHost configuration:
*:443 is a NameVirtualHost
default server ares.crucis.net (/etc/apache2/sites-enabled/ares.crucis.net-le-ssl.conf:2)
port 443 namevhost ares.crucis.net (/etc/apache2/sites-enabled/ares.crucis.net-le-ssl.conf:2)
alias crucis.net
port 443 namevhost crucis-court.com (/etc/apache2/sites-enabled/crucis-court.com-le-ssl.conf:2)
alias www.crucis-court.com
port 443 namevhost crucis.net (/etc/apache2/sites-enabled/crucis.net-le-ssl.conf:2)
alias www.crucis.net
*:80 is a NameVirtualHost
default server crucis-court.com (/etc/apache2/sites-enabled/crucis-court.com-le-ssl.conf:14)
port 80 namevhost crucis-court.com (/etc/apache2/sites-enabled/crucis-court.com-le-ssl.conf:14)
alias www.crucis-court.com
port 80 namevhost crucis-court.com (/etc/apache2/sites-enabled/crucis-court.com.conf:1)
alias www.crucis-court.com
port 80 namevhost crucis.net (/etc/apache2/sites-enabled/crucis.net.conf:1)
alias www.crucis.net
There shouldn't be a "port 80" virtualhost in the crucis-court.com-le-ssl.conf file.
Also, where did the file /etc/letsencrypt/live/ares.crucis.net-0001/fullchain.pem go? Did you delete certificates from Certbot perhaps without reading the documentation? Can you show the output of the command sudo certbot certificates please?
I entered "apache2ctl configtest and got this result.
AH00526: Syntax error on line 8 of /etc/apache2/sites-enabled/ares.crucis.net-le-ssl.conf:
SSLCertificateFile: file '/etc/letsencrypt/live/ares.crucis.net-0001/fullchain.pem' does not exist or is empty
Action 'configtest' failed.
In fact, the directory is gone. It did exist, now it doesn't So. How do I recreate the cert? I can't using certbot. I built this server and its certs six months ago. I've major surgery since and don't remember how I did it.
Update: I've been able to get certbot running and have recreated certs for one VHOST (crucis.net). However, I seem to now have an Apache2 VHOST issue with the second domain (crucis-court.com).
Please see my post above with regard to the double port 80 virtualhost. Notice there are two port 80 virtualhosts for crucis-court.com/www.crucis-court.com.
And? Does this mean I can only have one VHOST? Which cert should I use for crucis-court.com? Supporting a second domain didn't use to be so difficult. Course that was 15 years ago and that system worked until it crashed last year. I'm now relearning how to support two domains with Apache2.
So, what is the significance of having two domains on the same port?
You can have a multitude of virtual hosts. It's just not recommended to have two virtualhosts for the same set of domain names: because which virtualhost will be used? It doesn't make sense to have a duplicate virtualhost.
No, that's not what I'm saying. The only thing I'm saying is that you have TWO files, crucis-court.com.conf and crucis-court.com-le-ssl.conf BOTH have a port 80 virtualhost for crucis-court.com with alias www.crucis-court.com. That's one too much. Usually the crucis-court.com-le-ssl.conf configuration file ONLY has the port 443 virtualhost.
I'm not sure I can explain it any simpler than this.