Certbot-auto renew error - o such file or directory

Help
1

Please fill out the fields below so we can help you better.

My domain is:tutt.duckdns.org

I ran this command: certbot-auto renew

It produced this output:

Processing /etc/letsencrypt/renewal/tutt.duckdns.org.conf

Cert is due for renewal, auto-renewing…
Renewing an existing certificate
Performing the following challenges:
tls-sni-01 challenge for tutt.duckdns.org
Waiting for verification…
Cleaning up challenges
Attempting to renew cert from /etc/letsencrypt/renewal/tutt.duckdns.org.conf produced an unexpected error: [Errno 2] No such file or directory: ‘/etc/letsencrypt/archive/tutt.duckdns.org/privkey2.pem’. Skipping.

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/tutt.duckdns.org/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)

My web server is (include version): standalone

The operating system my web server runs on is (include version):raspbian (raspberri pi 3)

My hosting provider, if applicable, is: N/A

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

Also note, when I view the contents of the /etc/letsencrypt/archive/tutt.duckdns.org folder it contains the following files:
cert1.pem chain1.pem fullchain1.pem privkey1.pem

I am not sure why it is looking for privkey2.pem

Thanks for any assistance.

2

hi @ptutt1

can you paste the contents of /etc/letsencrypt/renewal/tutt.duckdns.org.conf please

Andrei

3

And maybe also the log from /var/log/letsencrypt.

4

renew_before_expiry = 30 days
version = 0.10.1
archive_dir = /etc/letsencrypt/archive/tutt.duckdns.org
cert = /etc/letsencrypt/live/tutt.duckdns.org/cert.pem
privkey = /etc/letsencrypt/live/tutt.duckdns.org/privkey.pem
chain = /etc/letsencrypt/live/tutt.duckdns.org/chain.pem
fullchain = /etc/letsencrypt/live/tutt.duckdns.org/fullchain.pem

Options used in the renewal process

[renewalparams]
authenticator = standalone
installer = None
account = ac08d43377ced741d3299700d6562882

5

2017-07-29 18:45:01,448:DEBUG:certbot.main:certbot version: 0.16.0
2017-07-29 18:45:01,450:DEBUG:certbot.main:Arguments: []
2017-07-29 18:45:01,451:DEBUG:certbot.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#apache,PluginEntryPoint#manual,PluginEntryPoint#nginx,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2017-07-29 18:45:01,535:DEBUG:certbot.log:Root logging level set at 20
2017-07-29 18:45:01,537:INFO:certbot.log:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2017-07-29 18:45:01,688:DEBUG:certbot.plugins.selection:Requested authenticator <certbot.cli._Default object at 0x75c296b0> and installer <certbot.cli._Default object at 0x75c296b0>

6

I have moved to install Hass.IO instead, which hopefully helps to remove some of these headaches.