It produced this output:
Cert not yet due for renewal
My operating system is (include version):
fedora 25
My web server is (include version):
cert created with certonly
My hosting provider, if applicable, is:
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):
I used the follow command to create the cert:
certbot -d www.segtravel.com --manual --preferred-challenges dns certonly
How can I use certbot to renew a domain with this configuration? How can I use certbot to print out on the command-line the cert expiration times for all the certs I have created?
I already received an email informing me it’s due for renewal. If it expires in nine days, when will I be able to renew it?
Is it possible to extend the time valid to more than 50 or 60 days? Or is this something I should expect to do every few months? With more than ten certs, this could become time-intensive.
Let's Encrypt checks whether your certificate has already been renewed, by checking if you've got a new certificate for the exact same set of domains. According to crt.sh, your old certificate covered bothsegtravel.com and www.segtravel.com, while your new one covers www.segtravel.com only. (The covered domains for each certificate are listed under "X509v3 Subject Alternative Name"). This isn't considered to be a "renewal" as it's a certificate for a different set of domains, which is why the email was sent.
If you only wanted a certificate for www.segtravel.com you can safely ignore the email. If you wanted a renewed certificate for both domains, you can obtain one by running the certbot command again, but this time specifying the full list of domains you want covered, e.g.:
certbot -d www.segtravel.com -d segtravel.com --manual --preferred-challenges dns certonly
Let's Encrypt certificate are actually valid for 90 days, but can't be extended any longer than that. To avoid spending time on renewals, you could maybe try a different validation method (e.g. webroot), or perhaps a different client (e.g. acme.sh), so that you can more easily automate the renewal process.