The scripts's discuss from cliffalbert

scripts's Issues

tls-sni deprecation

certbot is deprecating tls-sni authentication, which is what your scripts currently rely on. See https://community.letsencrypt.org/t/upcoming-tls-sni-deprecation-in-certbot/76383 for details. Any plans to update your scripts to use one of the other authentication methods (tls-alpn-01,http-01,dns-01) instead?

Using custom Certbot for latest acme-v02

Acme-v01 is no longer accepted and an error is present each time on renewal.

Attempting to renew cert (wireless.*******.com) from /etc/letsencrypt/renewal/wireless.*******.com.conf produced an unexpected error: urn:acme:error:servers.io/ for more details.. Skipping.
All renewal attempts failed. The following certs could not be renewed:

Can we add Let's Encrypt options --no-self-upgrade to the command line options since most users will have to use a manual installed Certbot-Auto.

# Command line options depending on New or Renew.
NEWCERT="--no-self-upgrade --renew-by-default certonly"
RENEWCERT="--no-self-upgrade -n renew"

And also change acme-v01 URL to acme-v02.

if [[ ${onlyinsert} != "yes" ]]; then
        echo "Firing up standalone authenticator on TCP port 443 and requesting cert..."
        ${LEBINARY} \
                --server https://acme-v02.api.letsencrypt.org/directory \
        --agree-tos \
                --standalone \
        ${LEOPTIONS}

I tested on Debian 9 and it works.

Recommend Projects