Plugins selected: Authenticator standalone, Installer None
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
tls-sni-01 challenge for benrothman.org
tls-sni-01 challenge for www.benrothman.org
TLS-SNI-01 is deprecated, and will stop working soon.
Cleaning up challenges
Attempting to renew cert (benrothman.org) from /etc/letsencrypt/renewal/benrothman.org.conf produced an unexpected error: Problem binding to port 443: Could not bind to IPv4 or IPv6.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/benrothman.org/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/benrothman.org/fullchain.pem (failure)
thank you so much for stickin with me forā¦ wow almost 4 hours? if you lived near me Iād buy you a beer but I think you live in Australia which is a problem, lol
No!!! The point of all this pain was to make it automatic. Your server will renew the certificate on its own and reload nginx on itās own. If you died today, it should keep renewing on its own forever.
haha oh ok awesome! I tried to set up a crontask for this last year but I could never get it to work. If it works now then awesome. Lol, Iāve thought about that, what if someone who runs a website makes a crontask or an autorenewal for their hosting subscription and then dies. It will just always be there until the world ends, lol
@_az Omfg. I was upgrading my server and it messed up the certbot installation, so I am back to letsencrypt rather than certbot . I am reading the convo from above but I do not see the solution! Do you remember how we installed certbot rather than letsencrypt?
yes thank you old friend, it is fixed nowā¦ (that was a lot quicker than last time) itās a good thing this thread had not expired yetā¦ another week or two and it would all be gone XD