My domain is:
I ran this command:
It produced this output:
The following certs are not due for renewal yet:
/usr/local/etc/letsencrypt/live/waylandgroup.com/fullchain.pem expires on 2019-02-18 (skipped)
No renewals were attempted.
But the certificate in live/ was expired a couple of days ago. Yet certbot insisted the certificate expired in February.
We are running cerbot renew on a daily basis with a cron:
0 0,12 * * * /usr/local/bin/python2.7 -c ‘import random; import time; time.sleep(random.random() * 3600)’ && /usr/local/bin/certbot renew
We believe the final customer at some point relocated the DNS to a different server and re-issued a new certificate and this somehow confused certbot on the original server. It other words, the DNS records for the base domain and www were pointed temporarily to a different server, a certificate re-issued there and then the DNS was pointed back to our server at 126.96.36.199
But we have no way to prove or disprove this, or otherwise explain why certbot got confused.
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
We ARE the hosting provider. But we don’t have control over the DNS of this particular domain.
I can login to a root shell on my machine (yes or no, or I don’t know):
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):