Closed ogallagher closed 4 years ago
I finally figured out the issue!! I’m using a load balancer that acts as a middleman between the client and its assigned web server instance (I was trying to prepare for future scalability). In addition to the web server instance needing the renewed certificate, I also needed to assign the new one to the load balancer.
For documentation’s sake, I’ve switched hosting to Dreamhost and have removed use of a load balancer. As a side effect, the nodejs server lifecycle is now being handled by Passenger, and the TLS certificate (including auto-updating 30 days prior to expiry) and http/https traffic is being handled automatically.
My setup is based loosely on this tutorial, and I understand that updating the LetsEncrypt cert should be as simple as running
certbot renew
and making sure the server shares the new .pem files. However, though I think I’ve done these steps, the certificate as shown to the client’s browser still says it’ll expire on the old date. I’m not sure what I’m missing.EDIT: I confirmed I didn’t renew the certificate; it’s still expired.