-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 with Gandi DNS challenge and API key not working in version 5.0.18 #3625
Comments
If you execute |
Exact same issue on my side. If I use gandi_token instead of gandi_api_key in the add-on YAML configurations, renewing the certificate works.
|
Same |
Hit this bug as well. As noted by @marcoce7, I was able to switch to using a Gandi Personal Access Token and the |
Same for me, with the latest update both token and api key give me the "Unable to get base domain for XXX" error. |
Solved for me. I have updated my configuration file |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The issue is still there and not solved. |
Describe the issue you are experiencing
In version 5.0.18 of the Let's Encrypt add-on, renewing with Gandi DNS challenge and API key does not work any more.
The relevant lines in the add-on logs are:
I didn't change the configuration with respect to a previous version that was working correctly.
I noticed that since #3581 the dns_gandi_api_key is added to /data/dnsapikey in
https://github.com/home-assistant/addons/blob/master/letsencrypt/rootfs/etc/services.d/lets-encrypt/run#L118-L121
but dns_gandi_api_key is added to /data/dnsapikey also in
https://github.com/home-assistant/addons/blob/master/letsencrypt/rootfs/etc/cont-init.d/file-structure.sh#L49
So the duplicated keyword name error make sense.
However, I do not know how to access the Certbot logs and files in the add-on container while running to check this.
If I use gandi_token instead of gandi_api_key in the add-on YAML configurations, renewing the certificate works.
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.0.18
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
No response
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: