mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-01-11 22:30:44 +01:00
Unknown hook sync-cert #500
Reference in New Issue
Block a user
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?
Originally created by @burl23 on GitHub (Oct 15, 2020).
I ran dehydrate -c and got some error messages that it said to ignore until I got the message unknown hook syn-cert. Here are the messages I received:
beryl@rock64:~/dehydrated$ ./dehydrated -c
INFO: Using main config file /home/beryl/dehydrated/config
Unknown hook this_hookscript_is_broken__dehydrated_is_working_fine__please_ignore_unknown_hooks_in_your_script
Processing rock64ha.duckdns.org
Unknown hook this_hookscript_is_broken__dehydrated_is_working_fine__please_ignore_unknown_hooks_in_your_script
OK
OK
Unknown hook sync_cert
[sudo] password for beryl:
Failed to restart home-assistant@homeassistant.service: Unit home-assistant@homeassistant.service not found.
ERROR: deploy_cert hook returned with non-zero exit code
Now I apparently don't have a !secret file so configuration.yaml won't load. What can I do?
@lukas2511 commented on GitHub (Oct 15, 2020):
This is not a dehydrated issue, this is an issue with your hook script and/or the software you are using.
The hooks in the wiki are user supplied and I'm not providing any kind of support for those.
@burl23 commented on GitHub (Oct 16, 2020):
Thank you for the advice to look at the hook script. After a while I found the error and everything is good now.
Sent from Mail for Windows 10
From: Lukas Schauer
Sent: Thursday, October 15, 2020 5:16 PM
To: dehydrated-io/dehydrated
Cc: burl23; Author
Subject: Re: [dehydrated-io/dehydrated] Unknown hook sync-cert (#772)
This is not a dehydrated issue, this is an issue with your hook script and/or the software you are using.
The hooks in the wiki are user supplied and I'm not providing any kind of support for those.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.