in the past, I had to renew the certificate manually every 3 months, but in the last 6 months Cloudflare made some updates to their website and I moved from a1astudios.tk to a1astudios.net. the SSL is renewing automatically now which is not a bad thing. I was wondering if let's encrypt has made updates to have all certificates renew automatically from now on, just wondering. thank you
It produced this output: The following certificates are not due for renewal yet:
/etc/letsencrypt/live/a1astudios.net/fullchain.pem expires on 2022-12-23 (skipped)
No renewals were attempted.
My web server is (include version): Ubuntu 20.04 x64
The operating system my web server runs on is (include version):Ubuntu 20.04 x64
My hosting provider, if applicable, is:Vult
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): using bash on MacBook pro command line
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):not sure
According to a tutorial from a developer that was the way it was done unless you modify the code to have it run on auto. Strait from the box packages installation required renewal every 3 months
According to a tutorial from a developer that was the way it was done unless you modify the code to have it run on auto. Strait from the box packages installation required renewal every 3 months, by the way, the SSL certificate is version 3
and this does appear in a "Version" field inside the certificate. (Browsers don't might not show this field, but, for example, openssl x509 does.) However, this isn't very relevant information for any kind of debugging issue because all certificates have been X.509v3 for decades.
Well, in most browsers on Windows that use the OS trust store, clicking through to get certificate details brings up the Windows dialog that describes the certificate, and that "Details" tab has "V3" in the version, as the very first property.
Oops, yeah! Thanks for the correction. So browsers sure enough can show that field.
I can see where that has the look of relevant information, too, since it's right up at the top. Even though you will never see anything other than 3 here for many reasons spread out across the whole web PKI ecosystems.
