Renewal Failed authorization procedure


#1

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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: One of 4 domains that are directed to my office is springfield74.org - the other 3 certificates also need to be renewed and I assume that the issue here is same as other servers.

I ran this command: sudo certbot renew --dry-run

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/lodge.springfield74.org.conf


Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator nginx, Installer nginx
Renewing an existing certificate
Performing the following challenges:
tls-sni-01 challenge for lodge.springfield74.org
tls-sni-01 challenge for www.springfield74.org
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (lodge.springfield74.org) from /etc/letsencrypt/renewal/lodge.springfield74.org.conf produced an unexpected error: Failed authorization procedure. www.springfield74.org (tls-sni-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Error getting validation data, lodge.springfield74.org (tls-sni-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Error getting validation data. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/lodge.springfield74.org/fullchain.pem (failure)


** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/lodge.springfield74.org/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)


1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: www.springfield74.org
    Type: connection
    Detail: Error getting validation data

    Domain: lodge.springfield74.org
    Type: connection
    Detail: Error getting validation data

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

My web server is (include version): Nginx 1.14 (other 3 domains are on an Apache server)

The operating system my web server runs on is (include version): Ubuntu 18.04

My hosting provider, if applicable, is: self hosted

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

This server is behind a proxy (Nginx) - https traffic is distributed between 3 servers based on host name (sni) The site is accessible via https. While trying to troubleshoot - deleted certificate of another domain (on Apache Server) once I can renew this server and the apache server I will tackle recreating that certificate.

I have no idea where to start looking for a solution.


#2

Hi,

Where did you requested that certificate?

By the way, TLS-SNI-01 is disabled for new subscriber for security purposes, and you might want to use HTTP-01 instead (since that will be disabled next year)

If you use HTTP-01, you might want to serve the records directly from your load balancer / proxy.

Thank you


#3

Certificate was requested on 9/20/18 using:
sudo certbot --nginx -d lodge.springfield74.org -d www.springfield74.org

When you say “serve records directly” do you mean terminate ssl on on load balancer/proxy?


#4

Got the certificates to renew. Changed port forward of http on my firewall from my proxy to the springfield74 server IP and Forced use of http (–preferred-challenges http).

I guess something is not right with my proxy forwarding http requests to the correct server.