Could not renew certificates

Please fill out the fields below so we can help you better.

My domain is:
conference.iai.int
I ran this command:
./certbot-auto --force-renewal
It produced this output:
Certbot doesn’t know how to automatically configure the web server on this system.
My web server is (include version):
latest nginx
The operating system my web server runs on is (include version):
Ubuntu Server 16.04
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): No

I’ve tried also certbot-only renew …see the results:
Requesting root privileges to run certbot…
/home/deploy/.local/share/letsencrypt/bin/letsencrypt renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/conference.iai.int.conf

Cert not yet due for renewal

The following certs are not due for renewal yet:
/etc/letsencrypt/live/conference.iai.int/fullchain.pem (skipped)
No renewals were attempted.
deploy@ubunturuby:~$ ./certbot-auto renew
Requesting root privileges to run certbot…
/home/deploy/.local/share/letsencrypt/bin/letsencrypt renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/conference.iai.int.conf

Cert not yet due for renewal

The following certs are not due for renewal yet:
/etc/letsencrypt/live/conference.iai.int/fullchain.pem (skipped)
No renewals were attempted.

It says not due for renewal, but I can’t access the site due too expired certificates. ???

@AlejandroF, it could be that your originally obtained the certificate with certonly, in which case Certbot didn’t install it for you, and also won’t handle restarting the web server upon renewal. This is actually rather likely since you’re using nginx and got your certificate a while ago; forms with certbot certonly --webroot were usually recommended for nginx users at that point.

You do have a renewed, currently-valid certificate for your domain already

https://crt.sh/?id=138693393

so there should be no need to renew it right now. However, your server is currently not using that certificate. Getting it to use it could be as simple as restarting nginx.

I just checked and it looks like you’ve already resolved the problem on your own.

If the problem turned out to be just about needing to restart nginx, you can do something like certbot-auto renew --renew-hook "service nginx graceful" in crontab, to tell Certbot to reload nginx for you if a renewal happens.

I did. I’m like a dog with a bone when I have problems… will not let go until I solve it.
Thanks anyway!Alejandro

Will do. This was unknown to me.
Alejandro

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.