> grep -Ri 90days /etc/letsencrypt/ /etc/letsencrypt/renewal/90daysofdance.com.conf:archive_dir = /etc/letsencrypt/archive/90daysofdance.com /etc/letsencrypt/renewal/90daysofdance.com.conf:cert = /etc/letsencrypt/live/90daysofdance.com/cert.pem /etc/letsencrypt/renewal/90daysofdance.com.conf:privkey = /etc/letsencrypt/live/90daysofdance.com/privkey.pem /etc/letsencrypt/renewal/90daysofdance.com.conf:chain = /etc/letsencrypt/live/90daysofdance.com/chain.pem /etc/letsencrypt/renewal/90daysofdance.com.conf:fullchain = /etc/letsencrypt/live/90daysofdance.com/fullchain.pem
Try:
certbot update_symlinks
certbot --apache --reinstall --cert-name 90daysofdance.com`
I don’t understand the program logic here.
It can’t continue because it can’t delete a file that is already deleted…
Lets try giving it a file that it can delete.
rm -r /etc/apache2/sites-available/90daysofdance.com-le-ssl.conf
sudo echo "#delete-me" >> /etc/apache2/sites-available/90daysofdance.com-le-ssl.conf
then try (again):
certbot --apache --reinstall --cert-name 90daysofdance.com
If the reinstall fails after that, then please show this file (in its’ entirety):
/etc/apache2/sites-available/90daysofdance.com.conf
[the previous post appears incomplete]
1 Like
Is that the whole thing?
The StopIteration error is because Certbot doesn't work when there are RewriteCond directives without any corresponding RewriteRules.
That can easily be resolved by commenting them out or removing them, or by adding whatever RewriteRule is missing.
I don't know about the other issue(s) in this thread, though.
2 Likes
It seems the problem is within the file
/etc/apache2/sites-available/90daysofdance.com.conf
which is needed by certbot to create the HTTPS version of it.
Compare that file with any other similar file.
Like:
/etc/apache2/sites-available/authorpower.com.conf
You may be able to repair it manually and then get certbot to reinstall.
There is nothing at all weird about the file. It’s the same as any non-SSL virtual host file:
<VirtualHost *:80>
DocumentRoot “/var/www/html/90daysofdance”
ServerName 90daysofdance.com
ServerAlias .90daysofdance.com
<Directory “/var/www/html/90daysofdance”>
Options FollowSymLinks
AllowOverride All
Require all granted
Require all granted
RewriteEngine on
RewriteCond %{SERVER_NAME} =.90daysofdance.com [OR]
RewriteCond %{SERVER_NAME} =90daysofdance.com
#1: It doesn't have a closing </VirtualHost> line
#2: The Rewrite section fails to do anything with those conditions.
#3: The <Directory> section doesn't have a closing </Directory> line
Please show a picture of the file instead.
Please show any one of those other files.
This domain behaves the same as 90daysofdance:
I set this one up by itself and it actually works. Here’s the conf:
And here’s the SSL file:
This one has a RewriteRule directive.
Yeah, that one works. But when I put the RewriteRule directive in the 90daysofdance one, it doesn’t. I even cloned the SSL from stitchditch and it failed.
Is there any way to completely, totally remove anything from LetsEncrypt and just start over as if it had never touched the system? Is there a list of files/directories to completely clean?
Just comparing your files… It maybe nothing, but is there any reason why there are no indents on those files for the sites that don’t work, but there are indents in the files for the site that does work?
Not that I know of. They were all tweaked by the Let’s Encrypt install process. Originally, everything was indented.
As a test, try it after removing lines:
9
11
12
13
1 Like