Open KitHubek opened 1 month ago
I am experiencing the exact same problem. i updated to 1.18.0 and that didn't help.
Same here!
DuckDNS Addon version 1.18.0
Same Here with 1.18.0.
The UI configuration is incorrect for duckdns. There are actually 2 errors. Edit in YAML. (click on 3 dots) It should be:
domains:`
- *****.duckdns.org
email: *****
keyfile: privkey.pem
certfile: fullchain.pem
challenge: dns
dns:
provider: dns-duckdns
duckdns_token: *****
Thank you to Bruno at https://www.derekseaman.com/2023/06/home-assistant-auto-renewing-lets-encrypt-ssl.html and Marie-Luise Orland
The UI configuration is incorrect for duckdns. There are actually 2 errors. Edit in YAML. (click on 3 dots) It should be:
domains:` - *****.duckdns.org email: ***** keyfile: privkey.pem certfile: fullchain.pem challenge: dns dns: provider: dns-duckdns duckdns_token: *****
Thank you to Bruno at https://www.derekseaman.com/2023/06/home-assistant-auto-renewing-lets-encrypt-ssl.html and Marie-Luise Orland
Thanks a lot ! Worked for me
The UI configuration is incorrect for duckdns. There are actually 2 errors. Edit in YAML. (click on 3 dots) It should be:
domains:` - *****.duckdns.org email: ***** keyfile: privkey.pem certfile: fullchain.pem challenge: dns dns: provider: dns-duckdns duckdns_token: *****
Thank you to Bruno at https://www.derekseaman.com/2023/06/home-assistant-auto-renewing-lets-encrypt-ssl.html and Marie-Luise Orland
This configuration is for the DuckDNS addon or for the Let's Encrypt addon ? Cause if I set this up like that in the DuckDNS addons, I got an error:
Failed to save add-on configuration, Missing option 'lets_encrypt' in root in Duck DNS (core_duckdns). Got {'domains': ['***.duckdns.org'], 'email': '***', 'keyfile': 'privkey.pem', 'certfile': 'fullchain.pem', 'challenge': 'dns', 'seconds': 300, 'dns': {'provider': 'dns-duckdns', 'duckdns_token': '***''}}
In the DuckDNS add-on, click on the three dots to get to "Edit in YAML". That is where you put your code. You need to register your domain with DuckDNS and copy DuckDNS token at the top of the page.
Describe the issue you are experiencing
Just see this error at log. Official HA addon Duck DNS All working ok, but recent see this error at log
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?
Duck DNS
What is the version of the add-on?
1.17.0
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1384 Downloaded Repositories | 9AccuWeather
can_reach_server | ok -- | -- remaining_requests | 33Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okGIOŚ
can_reach_server | ok -- | --Home Assistant Supervisor
host_os | Home Assistant OS 12.4 -- | -- update_channel | stable supervisor_version | supervisor-2024.06.2 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 234.0 GB disk_used | 31.2 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | generic-x86-64 supervisor_api | ok version_api | ok installed_addons | Studio Code Server (5.15.0), Mosquitto broker (6.4.1), Samba share (12.3.1), Duck DNS (1.17.0), NGINX Home Assistant SSL proxy (3.9.0), Zigbee2MQTT (1.38.0-1), ESPHome (2024.6.4), MariaDB (2.7.1), Advanced SSH & Web Terminal (18.0.0), phpMyAdmin (0.9.1), Node-RED (18.0.1)Dashboards
dashboards | 8 -- | -- resources | 5 views | 33 mode | storageRecorder
oldest_recorder_run | 3 maja 2024 17:04 -- | -- current_recorder_run | 30 czerwca 2024 00:07 estimated_db_size | 4754.19 MiB database_engine | mysql database_version | 10.11.6Spotify
api_endpoint_reachable | ok -- | --Xiaomi Miot Auto
component_version | 0.7.18 -- | -- can_reach_server | ok can_reach_spec | ok logged_accounts | 1 total_devices | 15Anything 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
my addon config:
domains:
at main HA config file:
http: ssl_certificate: /ssl/fullchain.pem ssl_key: /ssl/privkey.pem