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. https://crt.sh/?q=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: gjschaller.homeftp.net
I ran this command: (Script, see below)
It produced this output: (Verbose, see below)
My web server is (include version): Apache 2.4
The operating system my web server runs on is (include version): ReadyNAS OS 6.10.3 (Debian Jessie)
My hosting provider, if applicable, is: (N/A)
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): 1.3.0
===
I have an automated script that runs nightly to check for, and renew, my certificate. It seems to do the renew without issue. However, it did not replace the old cert with the new one.
Script:
/opt/letsencrypt/certbot-auto renew --standalone --pre-hook “service apache2 stop” --post-hook “service apache2 start”
Output:
root@GeoffNAS:/home/admin/crontab# ./LetsEncrypt-Renew.sh
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/gjschaller.homeftp.net.conf
Cert not yet due for renewal
The following certs are not due for renewal yet:
/etc/letsencrypt/live/gjschaller.homeftp.net/fullchain.pem expires on 2020-06-14 (skipped)
No renewals were attempted.
No hooks were run.
It looks like the new cert is there, but it’s not updating it for Apache. Anything I am missing or doing wrong?