Can't renew cert on raspberry pi nginx

Help
1

My domain is: home.sitelog.nz

I ran this command: sudo certbot renew

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

Processing /etc/letsencrypt/renewal/home.sitelog.nz.conf

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

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/home.sitelog.nz/fullchain.pem (failure)

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

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: home.sitelog.nz
    Type: connection
    Detail: 203.109.147.164: Fetching
    http://home.sitelog.nz/.well-known/acme-challenge/DWOj14pUh1wTcqlrVG4weZ_R851LMPHB3pnKdhCOyTo:
    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.10.3

The operating system my web server runs on is (include version):
Operating System: Raspbian GNU/Linux 9 (stretch)
Kernel: Linux 4.14.79-v7+
Architecture: arm

My hosting provider, if applicable, is: Self-hosted with a static IP

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 0.28.0

1 Like
2

Welcome to the community @jakewanny

I can't reproduce that error. I see your long consistent history of getting a cert although something has changed since your Mar25 cert. Your history suggests you should have renewed in late May but it has failed.

So, you should focus on any changes since Mar25. The error indicates a failure to respond to an HTTP request so has any networking equipment changed? Or, any major changes to your nginx config?

I would need to see the log to give any further advice. Could you upload or paste the entire contents of the log file in /var/log/letsencrypt for this failed request. There may be multiple log files so the one for this failure. To upload may require you to copy the .log file to a .txt file first.

If I don't say this some other volunteer will ... your Certbot version is very old. Please refer to https://certbot.eff.org for install options. Your other system parts are also very old. I don't think it is causing this specific problem but letting yourself get that far behind can cause a wide variety of problems.

2 Likes
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.