-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let's Encrypt: dns_transip_global_key should be yes or no #3876
Comments
Hm, I see the parameter has been introduced with #3835, and is now essentially mandatory for DNS challenge of type FWIW, the correct name of the add-on config option is |
Yep, that did work (without dns_). Thank you. |
Hi! Just wanted to share that my existing |
Would it be possible to somehow intercept these kinds of messages (like What I'm asking is a simple way to get notified in your dashboard that something needs to be looked at ASAP, without having to grind through the logs of all moving parts, integrations, add-ons and whatnot every other day. |
Same issue here. Would be great if errors like these would be shown as a HASS notification. |
Describe the issue you are experiencing
The renewal of my certificate is suddenly failing. I'm seeing the following error in the logs:
dns_transip_global_key
has been added to my addon config but it keeps failing and giving the same error message:Changing the value to no also doesn't change the behavior
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Let's Encrypt
What is the version of the add-on?
5.2.10
Steps to reproduce the issue
System Health information
There are currently no repairs pending
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: