starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-01-13 15:13:33 +01:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

Crontab #228

New Issue
Closed
opened 2025-12-29 01:19:21 +01:00 by adam · 6 comments
adam commented 2025-12-29 01:19:21 +01:00
Owner
Copy Link

Originally created by @dulemis on GitHub (Jun 26, 2017).

Having an issue with crontab. On the command line everything works, but in crontab the ouput of the same command is :

To use dehydrated with this certificate authority you have to agree to their terms of service which you can find here: https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf

To accept these terms of service run /jffs/LetsEncrypt/dehydrated --register --accept-terms.

However, I have already run the command with --register --accept-terms.

Originally created by @dulemis on GitHub (Jun 26, 2017). Having an issue with crontab. On the command line everything works, but in crontab the ouput of the same command is : To use dehydrated with this certificate authority you have to agree to their terms of service which you can find here: https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf To accept these terms of service run `/jffs/LetsEncrypt/dehydrated --register --accept-terms`. However, I have already run the command with --register --accept-terms.
adam closed this issue 2025-12-29 01:19:21 +01:00
adam commented 2025-12-29 01:19:22 +01:00
Author
Owner
Copy Link

@lukas2511 commented on GitHub (Jul 4, 2017):

For me it seems that dehydrated is using a different config / path than when you initially ran it.

I'd recommend setting the paths in a config file and tell your cronjob which config to use, just to be sure.

Normally this isn't necessary, but without any more information I have no idea what is wrong with your specific setup. Closing this issue for now since this seems like just a user error to me.

@lukas2511 commented on GitHub (Jul 4, 2017): For me it seems that dehydrated is using a different config / path than when you initially ran it. I'd recommend setting the paths in a config file and tell your cronjob which config to use, just to be sure. Normally this isn't necessary, but without any more information I have no idea what is wrong with your specific setup. Closing this issue for now since this seems like just a user error to me.
adam commented 2025-12-29 01:19:23 +01:00
Author
Owner
Copy Link

@dulemis commented on GitHub (Jul 16, 2017):

I also thought so, but I have tried running it with the -c flag to use the same config (which isn't needed when running it from the shell), but it returns the same. Any further ideas?

I m running it on a Linux embedded router, probably nbothing special.

@dulemis commented on GitHub (Jul 16, 2017): I also thought so, but I have tried running it with the -c flag to use the same config (which isn't needed when running it from the shell), but it returns the same. Any further ideas? I m running it on a Linux embedded router, probably nbothing special.
adam commented 2025-12-29 01:19:24 +01:00
Author
Owner
Copy Link

@txr13 commented on GitHub (Jul 16, 2017):

@dulemis The -c option is the command for cron mode. You'll want to try using the -f flag to specify the location of your config file.

@txr13 commented on GitHub (Jul 16, 2017): @dulemis The `-c` option is the command for cron mode. You'll want to try using the `-f` flag to specify the location of your config file.
adam commented 2025-12-29 01:19:24 +01:00
Author
Owner
Copy Link

@dulemis commented on GitHub (Jul 16, 2017):

Sorry, I meant --config.
Im redirecting the cron output to a textfile, and it logs at the top that its using the correct config. However, it still acts like its The first run...

@dulemis commented on GitHub (Jul 16, 2017): Sorry, I meant --config. Im redirecting the cron output to a textfile, and it logs at the top that its using the correct config. However, it still acts like its The first run...
adam commented 2025-12-29 01:19:24 +01:00
Author
Owner
Copy Link

@dulemis commented on GitHub (Aug 30, 2017):

Anyone having an idea why dehydrated thinks i'm running it for the first time in cron? I have specified the --config parameter, and everything works on the command line...

@dulemis commented on GitHub (Aug 30, 2017): Anyone having an idea why dehydrated thinks i'm running it for the first time in cron? I have specified the --config parameter, and everything works on the command line...
adam commented 2025-12-29 01:19:25 +01:00
Author
Owner
Copy Link

@dulemis commented on GitHub (Oct 3, 2017):

No one..?

@dulemis commented on GitHub (Oct 3, 2017): No one..?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complicated
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 suggestions wanted
testing
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#228
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?