root@proxy letsencrypt]# ./certbot-auto renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/valid.vc.conf
Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
tls-sni-01 challenge for valid.vc
tls-sni-01 challenge for old.valid.vc
tls-sni-01 challenge for test.valid.vc
Cleaning up challenges
Attempting to renew cert (valid.vc) from /etc/letsencrypt/renewal/valid.vc.conf produced an unexpected error: Problem binding to port 443: Could not bind to IPv4 or IPv6… Skipping.
Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
tls-sni-01 challenge for old.valid.vc
Cleaning up challenges
Attempting to renew cert (old.valid.vc) from /etc/letsencrypt/renewal/old.valid.vc.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/valid.vc/fullchain.pem (failure)
/etc/letsencrypt/live/old.valid.vc/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/valid.vc/fullchain.pem (failure)
/etc/letsencrypt/live/old.valid.vc/fullchain.pem (failure)
proxy letsencrypt]# sudo certbot renew --preferred-challenge http
sudo: certbot: command not found
[root@proxy letsencrypt]# ./certbot-auto renew --preferred-challenge http
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/valid.vc.conf
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 valid.vc
http-01 challenge for old.valid.vc
http-01 challenge for test.valid.vc
Cleaning up challenges
Attempting to renew cert (valid.vc) from /etc/letsencrypt/renewal/valid.vc.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6… Skipping.
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 old.valid.vc
Cleaning up challenges
Attempting to renew cert (old.valid.vc) from /etc/letsencrypt/renewal/old.valid.vc.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6… Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/valid.vc/fullchain.pem (failure)
/etc/letsencrypt/live/old.valid.vc/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/valid.vc/fullchain.pem (failure)
/etc/letsencrypt/live/old.valid.vc/fullchain.pem (failure)
If you want to get a new Letsencrypt-Certificate, you must show, that you are the owner of the domain. This is a challenge. SNI-Challenges are outdated.
The http-Challenge means: Letsencrypt gives you a long token (aödfadjfsaldfjsldfjasdlfjsdfdf) and you have to put a file under /.well-known/acme-challenge/ with this token as filename and a special content.
So http-Challenge requires an open http-Port 80. You can also check if you can use the dns-Challenge. Then you need to add a dns-entry.