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.
So create one certificate with all used domain names - non-www and www. May be the same with your other domain names, so you use one certificate with 8 domain names.
And you have some mixed content. Images via http instead of https. See the #Html-Content - part.
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.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Renewal configuration file /usr/local/etc/letsencrypt/renewal/theoceanwindow.com.conf produced an unexpected error: renewal config file {} is missing a required file reference. Skipping.
The following renewal configurations were invalid:
/usr/local/etc/letsencrypt/renewal/theoceanwindow.com.conf
My web server is (include version):Apache24
The operating system my web server runs on is (include version):Freebsd 12.1
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): certbot 1.3.0
I have messed up tai whole Certbot thing. How doe remove and Strat over
You could delete all of the contents of /etc/letsencrypt but this is probably a very bad idea:
It will make your web server configuration invalid if it refers to any of the certificates
It risks hitting Let's Encrypt issuance rate limits
According to the error message you mentioned before, this file seems to have some kind of problem, and if we could see its contents, we could probably tell you something that would improve the situation without having to start over!
Checking certificates gets me the following response
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Renewal configuration file /usr/local/etc/letsencrypt/renewal/theoceanwindow.com.conf produced an unexpected error: renewal config file {} is missing a required file reference. Skipping.
sudo cp /etc/letsencrypt/renewal/theoceanwindow.com-0001.conf /etc/letsencrypt/renewal/theoceanwindow.com.conf
sudo sed -i "s/-0001//g" /etc/letsencrypt/renewal/theoceanwindow.com.conf
This would give you a new copy of theoceanwindow.com.conf based on theoceanwindow.com-0001.conf, with the -0001s removed. This new copy might plausibly be correct for your existing certificate, and allow certbot renew to renew it properly.
I apologize, I think FreeBSD sed doesn’t support the same options as GNU sed on Linux. I am too used to Linux and will sometimes suggest Linux solutions without thinking.
sudo sed "s/-0001//g" /etc/letsencrypt/renewal/theoceanwindow.com.conf > /tmp/theoceanwindow.com.conf sudo cp /tmp/theoceanwindow.com.conf /etc/letsencrypt/renewal/theoceanwindow.com.conf
(The sudo doesn’t apply to the > redirection, but it doesn’t need to in this case.)
Ahhhno I didn'y. in fact when I do get the following error while the rest say they don't requite renewal
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/certbot/_internal/renewal.py", line 63, in _reconstitute
renewal_candidate = storage.RenewableCert(full_path, config)
File "/usr/local/lib/python3.7/site-packages/certbot/_internal/storage.py", line 466, in init
self._check_symlinks()
File "/usr/local/lib/python3.7/site-packages/certbot/_internal/storage.py", line 533, in _check_symlinks
"expected {0} to be a symlink".format(link))
certbot.errors.CertStorageError: expected /usr/local/etc/letsencrypt/live/theoceanwindow.com/cert.pem to be a symlink
Renewal configuration file /usr/local/etc/letsencrypt/renewal/theoceanwindow.com.conf is broken. Skipping.
What does the
-rw-r–r-- 1 root wheel 588 Jun 11 13:26 kasdivi.com-0001.conf
-rw-r–r-- 1 root wheel 623 Jun 11 13:27 theoceanwindow.com-0001.conf
These get created if you run Certbot with a -d list of domains that partially overlaps with, but is not a strict superset of, a certificate that you already have.
