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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Could you please try the renewal again and note down what the command was and what it said when it failed? There are many different errors possible, and the specific error message will help us to give you advice about what to do about it.
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for askbiblescholars.com
Cleaning up challenges
Attempting to renew cert (askbiblescholars.com) from /etc/letsencrypt/renewal/askbiblescholars.com.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6.. Skipping.
Attempting to parse the version 2.6.0 renewal configuration file found at /etc/letsencrypt/renewal/www.askbiblescholars.com.conf with version 0.40.0 of Certbot. This might not work.
Cert not yet due for renewal
Could not choose appropriate plugin for updaters: Could not select or initialize the requested installer nginx.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/askbiblescholars.com/fullchain.pem (failure)
The following certs are not due for renewal yet:
/etc/letsencrypt/live/www.askbiblescholars.com/fullchain.pem expires on 2023-09-19 (skipped)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/askbiblescholars.com/fullchain.pem (failure)
It seems that during your last renewal/issuance certbot was running in standalone mode.
This is not the preferred method when there is a working web service.
That said, you could probably stop your web server and renew the cert and then restart the web server.
Again, that is not an ideal renewal process.
If you can take the time to figure out how to use the web server OR use --webroot through the web server, you may be able to automate this in a manner that won't stop your web site [while renewing].
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for askbiblescholars.com
Cleaning up challenges
Attempting to renew cert (askbiblescholars.com) from /etc/letsencrypt/renewal/askbiblescholars.com.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6.. Skipping.
Attempting to parse the version 2.6.0 renewal configuration file found at /etc/letsencrypt/renewal/www.askbiblescholars.com.conf with version 0.40.0 of Certbot. This might not work.
Cert not yet due for renewal
Could not choose appropriate plugin for updaters: Could not select or initialize the requested installer nginx.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/askbiblescholars.com/fullchain.pem (failure)
The following certs are not due for renewal yet:
/etc/letsencrypt/live/www.askbiblescholars.com/fullchain.pem expires on 2023-09-19 (skipped)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/askbiblescholars.com/fullchain.pem (failure)
Well, apparently something is still listening on port 80. You could use e.g. sudo netstat -nap | grep 80 to find out which process.
This is weird. So currently you're using Certbot 0.40.0, a very old version, but somewhere in the past you've also used Certbot 2.6.0, one of the most recent versions? Did you install Certbot using multiple methods? E.g. aptandsnap perhaps? Is there currently just a single Certbot installed or multiple?
Looks like you have two separate certificates for the same domain. Can you please show the output of sudo certbot certificates ?
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Attempting to parse the version 2.6.0 renewal configuration file found at /etc/letsencrypt/renewal/www.askbiblescholars.com.conf with version 0.40.0 of Certbot. This might not work.
The goal is to use nginx to get/renew your certs. And, your root name askbiblescholars.com should give the same results as your www subdomain.
Getting to that takes several steps. I see your root domain responding poorly to various routine requests. So, let's fix that first. Can you upload the file from this command? If not, please post entire (long) output here with 3 backticks before and after the output.
sudo nginx -T >upload.txt
If you must paste it like this
```
output from command
```