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:
soccerdailynews.co (and 49 others across 3 servers)
note this site is in fact serving securely right now.
I ran this command:
sudo certbot --apache rollback
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Error while running apache2ctl configtest.
Action 'configtest' failed.
The Apache error log may have more information.
AH00526: Syntax error on line 36 of /etc/apache2/sites-enabled/000-default-le-ssl.conf:
SSLCertificateFile: file '/etc/letsencrypt/live/soccerdailynews.co/fullchain.pem' does not exist or is empty
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.2 LTS
My hosting provider, if applicable, is:
Amazon aws; it's an ec2 instance
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 1.18.0
This server has 17 virtual hosts, each serving up a wordpress site. Frankly, I did the apache config incorrectly at first, with all the vhosts in 000-default.conf, instead of each in its own conf file. Then (well many times) I ran certbot across all the extant domains as I built the server. By the time I moved on to the second (of three) servers, I realized the "right way" to do it , with individual conf files for each domain, and certbot cleanly added an le-ssl-conf for each virtual host file. I went back to reconfigure this one, but first I tried to rollback certbot with the above errors.
I tried just cleaning out sites-enabled/000-default-le-ssl.conf but certbot just rewrites it with lines pointing at non-existing or empty certs. So I tried deleting the certs with certbot --apache delete -d domainname.com
with no joy; certbot still writes them into the 000-default-le-ssl.conf so apache bails (with an error similar to the certbot error above). Which I guess is actually an apache error, anyway.
Another way to put this q is: how do I get back to a blank slate, removing everything certbot has done so far (without just rebuilding the server).