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 web server is (include version):
Node.JS 6.12.0
The operating system my web server runs on is (include version):
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.
I had previously successfully gotten certificates issued using acme-tiny (https://github.com/diafygi/acme-tiny) however when I attempt to renew a cert it issues the same old expired cert.
I have ever tried generated a new account key and following the steps outlined in the github from scratch, I still am getting the old certificate issued (expired 1/20/18, as can be seen here: https://foozstats.cacheblasters.com/message)
What steps am I missing to get it to issue a new cert instead of the same old expired one?
The certificate that you’ve just posted was issued today and expires on May 1. So something about your process of importing it into your web server seems to be the problem, not the certificate issuance itself.
Hey @OtherwiseJunk, I recently launched https://padlockspy.com for monitoring of SSLs, including expiry reminders, check it out if you’re interested. Let me know what you think