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.
It produced this output:
Certificate Name: www.ttlevelup.com
Domains: www.ttlevelup.comttlevelup.com
Expiry Date: 2020-01-08 16:28:15+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/www.ttlevelup.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/www.ttlevelup.com/privkey.pem
My web server is (include version): apache 2.2.15
The operating system my web server runs on is (include version): CentOS 6.9
My hosting provider, if applicable, is: GCP
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 0.39.0
Even though the above expiration shows 89 days till expiration, the certificate info in the browser shows yesterday. What could be wrong? I’ve been using LetsEncrypt for several years now without problems.
Fixed my problems by pointing all my /etc/httpd/conf.d/[domainname].com-le-ssl.conf to their corresponding /etc/letsencrypt/live/[domain] folders.
NOTES: For some reason, some of the letsencrypt live folders have www… and some do not.
I also wonder, now that each domain is not sharing an over-arching domain … will they renew automatically and correctly? We shall see …