Challenge validation has failed when running with cron #515

New Issue

adam · 2025-12-29T01:26:35+01:00

adam commented

2025-12-29 01:26:35 +01:00

Originally created by @cdarken on GitHub (Dec 21, 2020).

This happened suddenly, no idea what the issue can be, as it runs fine when I'm invoking it manually.
Using http-01 challenge type.

Originally created by @cdarken on GitHub (Dec 21, 2020). This happened suddenly, no idea what the issue can be, as it runs fine when I'm invoking it manually. Using http-01 challenge type.

adam closed this issue

2025-12-29 01:26:36 +01:00

adam commented

2025-12-29 01:26:36 +01:00

@j-ed commented on GitHub (Dec 21, 2020):

Without providing the full DETAILED output of the script it won't be possible to identify the root cause of the problem. Please update your positing and provide the missing information.

@j-ed commented on GitHub (Dec 21, 2020): Without providing the full DETAILED output of the script it won't be possible to identify the root cause of the problem. Please update your positing and provide the missing information.

adam commented

2025-12-29 01:26:37 +01:00

@cdarken commented on GitHub (Dec 21, 2020):

How do you suggest to get it? I only have the redirected output to a file. Can't see any detailed log switch to the script.
I only have this, for the last failed run:

Processing [domain_name]
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Dec 20 22:00:42 2020 GMT (Less than 10 days). Renewing!
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting new certificate order from CA...
 + Received 1 authorizations URLs from the CA
 + Handling authorization for [domain_name]
 + 1 pending challenge(s)
 + Deploying challenge tokens...
 + Responding to challenge for [domain_name] authorization...
 + Cleaning challenge tokens...
 + Challenge validation has failed :(

@cdarken commented on GitHub (Dec 21, 2020): How do you suggest to get it? I only have the redirected output to a file. Can't see any detailed log switch to the script. I only have this, for the last failed run: ``` Processing [domain_name] + Checking domain name(s) of existing cert... unchanged. + Checking expire date of existing cert... + Valid till Dec 20 22:00:42 2020 GMT (Less than 10 days). Renewing! + Signing domains... + Generating private key... + Generating signing request... + Requesting new certificate order from CA... + Received 1 authorizations URLs from the CA + Handling authorization for [domain_name] + 1 pending challenge(s) + Deploying challenge tokens... + Responding to challenge for [domain_name] authorization... + Cleaning challenge tokens... + Challenge validation has failed :( ```

adam commented

2025-12-29 01:26:37 +01:00

@cdarken commented on GitHub (Dec 30, 2020):

So I just caught another output like that in the server log. I modified the cron to execute it in the next minute to check the output and now it worked! Any other ideas?

@cdarken commented on GitHub (Dec 30, 2020): So I just caught another output like that in the server log. I modified the cron to execute it in the next minute to check the output and now it worked! Any other ideas?

adam commented

2025-12-29 01:26:37 +01:00

@hnnweb commented on GitHub (Jan 10, 2021):

What did you change ?

( To be helpful upon others, you should provide every step you did to help the community )

@hnnweb commented on GitHub (Jan 10, 2021): What did you change ? ( To be helpful upon others, you should provide every step you did to help the community )

adam commented

2025-12-29 01:26:40 +01:00

@cdarken commented on GitHub (Jan 10, 2021):

Change from what? From the previous run when it failed?

@cdarken commented on GitHub (Jan 10, 2021): Change from what? From the previous run when it failed?

adam commented

2025-12-29 01:26:40 +01:00

@lukas2511 commented on GitHub (Feb 18, 2021):

This may just be related to some Let's Encrypt downtimes. I recommend checking their status page at https://letsencrypt.status.io if this happens again.

@lukas2511 commented on GitHub (Feb 18, 2021): This may just be related to some Let's Encrypt downtimes. I recommend checking their status page at https://letsencrypt.status.io if this happens again.

adam commented

2025-12-29 01:26:40 +01:00

@cdarken commented on GitHub (Feb 18, 2021):

Thanks! I remember I saw recently some social media posts about their new hardware. Maybe it was due to the limitations of their old servers.

@cdarken commented on GitHub (Feb 18, 2021): Thanks! I remember I saw recently some social media posts about their new hardware. Maybe it was due to the limitations of their old servers.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#515