Auto renew issue


I am running Let’s Encrypt on an Ubuntu server. I followed step 4 in this guide to setup auto renewal via Cron. -

However the renewal fails and shows this in the log file:

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

If I run /opt/letsencrypt/letsencrypt-auto renew in the CLI the renewal works just fine.

Does anyone have any thoughts please?



I have a look into this more, The error show is below. However we have the DNS setup correctly. For outside we can get onto the sites.

I do see its connecting via HTTP, but Apache is setup to redirect http to https. could this be breaking it?


Type: connection
Detail: Could not connect to

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A 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.

If you add a file ( such as “test” with plain acsii text “success” in it ) to {webroot}/.well-known/acme-challenge/test can you reach it in a general browser from the internet ( not one specifically whitelisted ) at ?


I have done that, when i go to I can see the contents.


Is that your real domain name ? if so I can’t reach the file. If it isn’t - can you provide your real domain name for us to test please.

Its not the real domain name. is one of the real domain names.



Can you place a test file in {webroot}/.well-known/acme-challenge on that account please ( at the moment I get redirected to https, then redirected to www. but then I get a 404, file not found)

Can you see this?


yes - testworks

(sorry, was trying test not test.txt before )

going back to your original post, there seem to be 2 things, which may or not be connected.

Initially, you say that it works when run on the command line, and fails when run as a cron. This strikes me as either a permissions of path / environment variable issue.

Your second post is about the DNS issue … there was a DNS issue yesterday at the letsencrypt side. Was this just a temporary issue whilst you were testing ? and possibly no longer an issue ?

I was testing this just an hour ago and had the same issue.


I am having the same issue.

Running this command

/opt/letsencrypt/letsencrypt-auto renew >> /var/log/le-renew.log 

From a cron job give me the same error as ZFWT is seeing, However if I run the same command from a terminal it works fine.

I also checked on the lets encrypt log file located in /var/log/letsencrypt
Here is the full log file

Here is a section that I thought was interesting.
2016-07-03 06:00:05,860:INFO:certbot.renewal:Cert is due for renewal, auto-renewing…
2016-07-03 06:00:05,878:DEBUG:certbot.plugins.selection:Requested authenticator apache and installer apache
2016-07-03 06:00:05,940:DEBUG:certbot.plugins.disco:No installation (PluginEntryPoint#apache):
Traceback (most recent call last):
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot/plugins/”, line 105, in prepare
File “/root/.local/share/letsencrypt/local/lib/python2.7/site-packages/certbot_apache/”, line 161, in prepare
raise errors.NoInstallationError

So from what I gather for some reason it thinks Apache isn’t installed when the cron job runs.

The cron job is running as root, so it shouldn’t be any permission issues.

I have the same issue. When run from cron it fails. When run from the command line, it renews without error.

Does this help -


Did anyone manage to fix this please?


this is fixed in the Debian packages as of 0.8.1-2.

What is your setup and what is the exact issue you are seeing ? and have you tried correcting the PATH.

I have just had to run this manually as the certificate is close the expiring and I now get the errors all the time :frowning:

Ok, so no longer just happening when run as a cron for you. From the original post you say “If I run /opt/letsencrypt/letsencrypt-auto renew in the CLI the renewal works just fine.”

Can you ensure you are using the latest version of certbot, with verbose mode, and paste the log please ( it may be easier to paste it in )


I have just run the command manually again and it has worked and renewed all my certificates. Must have been a glitch?

But it still didn’t work as a Cron job.


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