Pb duckdns

djedje · Juillet 25, 2025, 9:05

Bonjour à tous,

je suis en train de configurer pour avoir acces à distance à mon HA via duckdns + ngnix
je bloque sur le message d’erreur suivant dans duckdns:
ERROR: deploy_challenge hook returned with non-zero exit code

j’ai testé pleins de trucs mais sans succès, j’ai vérifié mon token ‹ pas d’espace par exemple ›…
j’ai déinstallé l’add on… que dalle je bloque.

Redirection de port sur interface freebox semble ok sur port 49xxxx → @ip de mon HA port 8123.
test port ouvert depuis Port Scanners / WhatsMyIP.org

conf duckdns

domains:
  - xxxxxx.duckdns.org
token: xxxxxxxxxxxxxx
aliases: []
lets_encrypt:
  accept_terms: true
  algo: secp384r1
  certfile: /ssl/fullchain.pem
  keyfile: /ssl/privkey.pem
seconds: 300

configuration.yaml

http:
  server_port: 8123
  ip_ban_enabled: true
  login_attempts_threshold: 5

merci !

WarC0zes · Juillet 25, 2025, 9:11

Bonjour,
quel NGINX ?
NGINX Manager ou NGINX Home Assistant SSL Proxy ?
Tu es en IP FULLSTACK chez free ?

normalement duckdns :

domains:
  - votredomaine.duckdns.org
token: 35cdgql5-xxxx-xxxx-xxxx-6e2e6e8598e1
aliases: []
lets_encrypt:
  accept_terms: true
  algo: secp384r1
  certfile: fullchain.pem
  keyfile: privkey.pem
seconds: 300

configuration.yaml :

http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
  ip_ban_enabled: true
  login_attempts_threshold: 5

Redirection de port sur Freebox

Connectez-vous à votre Freebox via 192.168.1.254 ;
Allez à « Paramètres de la Freebox »,
Dans « Gestion des ports », cliquez sur « Ajouter une redirection » ;

IP Destination : IP de votre serveur Home Assistant
Redirection active : cochée
IP source : Toutes
Protocole : TCP
Port de début : 8123
Port de fin : 8123
Port de destination : 8123
Commentaire : Redirection DuckDNS

Pour duckdns et NGINX Home assistant SSL Proxy :

djedje · Juillet 25, 2025, 9:34

module utilisé sous HA: NGINX Home Assistant SSL proxy.

pour le redirect: l’interface ne permet pas de choisir un port inférieur à 49152 pour info pour le Port de début et Port de fin. j’ai pris un port donc > 49152 pour ces 2 parametres.

modif du configuration.yaml donne ceci:

Erreurs de configuration

Invalid config for ‹ http › at configuration.yaml, line 221: not a file for dictionary value ‹ http->ssl_certificate ›, got ‹ /ssl/fullchain.pem › Invalid config for ‹ http › at configuration.yaml, line 222: not a file for dictionary value ‹ http->ssl_key ›, got ‹ /ssl/privkey.pem ›

Tochy · Juillet 25, 2025, 9:43

Salut
Tu as bien mis les fichier ssl sur ton serveur HA ? (ou verifié qu’ils y sont, je me rappelle plus si c’est fait automatiquement)
Il te manque une partie également dans le configuration.yaml pour nginx

# Certificat SSL duckdns
http:
### Duck DNS ### Décommentez les 2 lignes SSL et commenter la partie NGINX si pas de NGINX
#  ssl_certificate: /ssl/fullchain.pem
#  ssl_key: /ssl/privkey.pem

### NGINX Home Assistant SSL proxy ###
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.0/24

djedje · Juillet 25, 2025, 10:05

comment puis je svp vérifier leur presence ?

j’ai modifie le configuration.yaml.

code error duckdns:
ERROR: deploy_challenge hook returned with non-zero exit code

djedje · Juillet 25, 2025, 12:27

bon j’ai tout repris, j’ai viré les addons, enlever les lignes dans la configuration.yaml …

et je reparametre DuckDns.

Voici le premier message d’erreur …

ERROR: Challenge is invalid! (returned: invalid) (result: [« type »] « dns-01 »

je reprecise, je suis derriere un ABO Free.

merci pour votre aide

WarC0zes · Juillet 25, 2025, 12:40

Il te faut passer en IP FULLSTACK chez free, pour avoir accès à tous les ports.
Ça te configure directement de la Freebox.

djedje · Juillet 25, 2025, 12:59

ok demande faite, je dois attendre 30’’ pour redemarrer le routeur.

Pourquoi est-ce nécessaire d’avoir une IP Fullstack .?

WarC0zes · Juillet 25, 2025, 1:07

Pour avoir un ip non partagé et avoir tous les ports disponible.

Dans un premier temps, il faut que duckdns se lance correcte avant de passer a la suite.

djedje · Juillet 25, 2025, 1:52

ok j’ai ca désormais
Terminated
ERROR: deploy_challenge hook returned with non-zero exit code
[15:30:12] WARNING:
[15:40:14] INFO: OK
xx.xx.xx.xx
UPDATED

WarC0zes · Juillet 25, 2025, 1:53

Montre le journal de duckdns complet stp . Juste la partie quand tu lances duckdns et que ca fini .
Utilise la balise texte préformaté pour coller le journal. Icône .

djedje · Juillet 25, 2025, 2:08

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service duckdns: starting
s6-rc: info: service duckdns successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
# INFO: Using main config file /data/workdir/config
+ Account already registered!
[16:05:35] INFO: Starting DuckDNS...
[16:05:36] INFO: Renew certificate for domains: xxxxxxxxxxxxxx.duckdns.org and aliases: 
# INFO: Using main config file /data/workdir/config
Processing xxxxx.duckdns.org
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting new certificate order from CA...
 + Received 1 authorizations URLs from the CA
 + Handling authorization for xxxxx.duckdns.org
 + 1 pending challenge(s)
 + Deploying challenge tokens...
Terminated
ERROR: deploy_challenge hook returned with non-zero exit code

WarC0zes · Juillet 25, 2025, 2:13

test en rajoutant ces lignes:

challenge: dns
dns:
  provider: dns-duckdns

domains:
  - ****.duckdns.org
token: **** 
aliases: []
lets_encrypt:
  accept_terms: true
  algo: secp384r1
  certfile: fullchain.pem
  keyfile: privkey.pem
seconds: 300
challenge: dns
dns:
  provider: dns-duckdns

github.com/home-assistant/addons

ERROR: deploy_challenge hook returned with non-zero exit code

ouvert 08:21AM - 27 Apr 25 UTC

fermé 10:06AM - 20 Jul 25 UTC

tigersoul925

stale

### Describe the issue you are experiencing Lately, I've not been able to updat…e DuckDNS anymore. Firstly I'm using an "alternative name" (alias) so for a long while back I've had to manually remove the alias, update the addon, then re-add the alias and update again due to the known bug. Now however, since a few weeks, it won't update in the last step anymore when I include the alias. I just get this: ` [04:47:22] INFO: Renew certificate for domains: xxx.duckdns.org and aliases: lan.xxx.se OKOK# INFO: Using main config file /data/workdir/config Processing xxx.duckdns.org with alternative names: lan.xxx.se + Checking domain name(s) of existing cert... changed! + Domain name(s) are not matching! + Names in old certificate: xxx.duckdns.org + Configured names: xxx.duckdns.org lan.xxx.se + Forcing renew. + Checking expire date of existing cert... + Valid till Jul 20 07:42:17 2025 GMT (Longer than 30 days). Ignoring because renew was forced! + Signing domains... + Generating private key... + Generating signing request... + Requesting new certificate order from CA... + Received 2 authorizations URLs from the CA + Handling authorization for xxx.duckdns.org + Handling authorization for lan.xxx.se + 2 pending challenge(s) + Deploying challenge tokens... Terminated ERROR: deploy_challenge hook returned with non-zero exit code ` I've tried for well over a week and it just won't work anymore. ### 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.90.0 ### Steps to reproduce the issue 1. Set a conf with an alias 2. Restart addon 3. See it fail and cry ... ### System Health information ## System Information version | core-2025.4.4 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.13.2 os_name | Linux os_version | 6.6.74-haos-raspi arch | aarch64 timezone | Europe/Stockholm config_dir | /config <details><summary>Home Assistant Community Store</summary> GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 5000 Installed Version | 2.0.5 Stage | running Available Repositories | 1682 Downloaded Repositories | 15 </details> <details><summary>Home Assistant Cloud</summary> logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok </details> <details><summary>Home Assistant Supervisor</summary> host_os | Home Assistant OS 15.2 -- | -- update_channel | stable supervisor_version | supervisor-2025.04.0 agent_version | 1.7.2 docker_version | 28.0.4 disk_total | 28.3 GB disk_used | 15.6 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | File editor (5.8.0), InfluxDB (5.0.2), Grafana (10.5.0), Glances (0.21.1), Log Viewer (0.17.1), Samba share (12.5.0), Mosquitto broker (6.5.0), Home Assistant Google Drive Backup (0.112.1), Studio Code Server (5.19.2), Advanced SSH & Web Terminal (20.0.2), Duck DNS (1.19.0), MariaDB (2.7.2), Nginx Proxy Manager (1.0.1), phpMyAdmin (0.11.1), UniFi Network Application (4.0.2), WireGuard (0.11.0), Rclone Backup (3.3.4) </details> <details><summary>Dashboards</summary> dashboards | 6 -- | -- resources | 9 views | 19 mode | storage </details> <details><summary>Network Configuration</summary> adapters | lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth5a76b45 (disabled), vethce378a5 (disabled), veth3c9f9d6 (disabled), vethfe625cc (disabled), veth1d35fe8 (disabled), vethb489f67 (disabled), veth7486d09 (disabled), vethd1ae8e4 (disabled), vethef30179 (disabled), vethd82531a (disabled), veth2c635a0 (disabled), veth08c1b93 (disabled), veth120439f (disabled), vethcf431ae (disabled) -- | -- ipv4_addresses | lo (127.0.0.1/8), end0 (192.168.1.79/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth5a76b45 (), vethce378a5 (), veth3c9f9d6 (), vethfe625cc (), veth1d35fe8 (), vethb489f67 (), veth7486d09 (), vethd1ae8e4 (), vethef30179 (), vethd82531a (), veth2c635a0 (), veth08c1b93 (), veth120439f (), vethcf431ae () ipv6_addresses | lo (::1/128), end0 (fe80::aa37:1c24:afb7:990a/64), hassio (fe80::5ccd:54ff:feba:e183/64), docker0 (fe80::3c0e:aff:fe75:6891/64), veth5a76b45 (fe80::8c6:38ff:fe3e:f06d/64), vethce378a5 (fe80::30b3:21ff:fed5:b248/64), veth3c9f9d6 (fe80::80c4:3aff:fe5b:6ac/64), vethfe625cc (fe80::182a:ff:fead:70b2/64), veth1d35fe8 (fe80::c04c:42ff:fe3f:2989/64), vethb489f67 (fe80::5c7a:3ff:fe36:f70d/64), veth7486d09 (fe80::7cf9:73ff:fe53:8844/64), vethd1ae8e4 (fe80::681c:39ff:fe84:46a5/64), vethef30179 (fe80::f8ff:6eff:fe65:cf09/64), vethd82531a (fe80::d029:3dff:fe90:5bf3/64), veth2c635a0 (fe80::ec98:ddff:fe4e:b4d6/64), veth08c1b93 (fe80::49f:92ff:fe57:b5ad/64), veth120439f (fe80::b4d6:91ff:feef:b16c/64), vethcf431ae (fe80::58f6:cff:fec5:fb2/64) announce_addresses | 192.168.1.79, fe80::aa37:1c24:afb7:990a </details> <details><summary>Recorder</summary> oldest_recorder_run | April 19, 2025 at 14:19 -- | -- current_recorder_run | April 25, 2025 at 15:11 estimated_db_size | 148.02 MiB database_engine | mysql database_version | 10.11.6 </details> <details><summary>Spotify</summary> api_endpoint_reachable | ok -- | -- </details> ### Anything in the Supervisor logs that might be useful for us? ```txt No, nothing of interest. ``` ### Anything in the add-on logs that might be useful for us? ```txt [04:47:22] INFO: Renew certificate for domains: xxx.duckdns.org and aliases: lan.xxx.se OKOK# INFO: Using main config file /data/workdir/config Processing xxx.duckdns.org with alternative names: lan.xxx.se + Checking domain name(s) of existing cert... changed! + Domain name(s) are not matching! + Names in old certificate: xxx.duckdns.org + Configured names: xxx.duckdns.org lan.xxx.se + Forcing renew. + Checking expire date of existing cert... + Valid till Jul 20 07:42:17 2025 GMT (Longer than 30 days). Ignoring because renew was forced! + Signing domains... + Generating private key... + Generating signing request... + Requesting new certificate order from CA... + Received 2 authorizations URLs from the CA + Handling authorization for xxx.duckdns.org + Handling authorization for lan.xxx.se + 2 pending challenge(s) + Deploying challenge tokens... Terminated ERROR: deploy_challenge hook returned with non-zero exit code ``` ### Additional information _No response_

djedje · Juillet 25, 2025, 2:17

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service duckdns: starting
s6-rc: info: service duckdns successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
# INFO: Using main config file /data/workdir/config
+ Account already registered!
[16:15:18] INFO: Starting DuckDNS...
[16:15:19] INFO: Renew certificate for domains: xxxxx.duckdns.org and aliases: 
# INFO: Using main config file /data/workdir/config
Processing xxxxx.duckdns.org
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting new certificate order from CA...
 + Received 1 authorizations URLs from the CA
 + Handling authorization for xxxxx.duckdns.org
 + 1 pending challenge(s)
 + Deploying challenge tokens...
OK + Responding to challenge for xxxxx.duckdns.org authorization...
 + Cleaning challenge tokens...
OK + Challenge validation has failed :(
ERROR: Challenge is invalid! (returned: invalid) (result: ["type"]	"dns-01"
["url"]	"https://acme-v02.api.letsencrypt.org/acme/chall/2552385101/558720350871/_aldJg"
["status"]	"invalid"
["validated"]	"2025-07-25T14:15:58Z"
["error","type"]	"urn:ietf:params:acme:error:dns"
["error","detail"]	"DNS problem: SERVFAIL looking up TXT for _acme-challenge.xxxxx.duckdns.org - the domain's nameservers may be malfunctioning"
["error","status"]	400
["error"]	{"type":"urn:ietf:params:acme:error:dns","detail":"DNS problem: SERVFAIL looking up TXT for _acme-challenge.xxxxx.duckdns.org - the domain's nameservers may be malfunctioning","status":400}
["token"]	"QnV6OQnM4Ei8VUy8AKm2PHRAU0B3Vs_N4evfSDATfmU")

WarC0zes · Juillet 25, 2025, 2:20

Duckdns est très instable , il faut retenter plus tard.

Regarde ce lien qui indique les états des services :
https://intodns.com/duckdns.org

J’ai abandonné duckdns , à cause de problème de connexion de plus en plus fréquent. J’ai pris un NDD chez OVH ( payant ) et depuis 2 ans plus de soucis.

djedje · Juillet 25, 2025, 2:32

ok
OVH .fr 4,99€/1ière année et ensuite 9,35€.TTC par an. cela me semble un bon compromis.

avant d’acheter, mon probleme est lié à l’instabilité de duckdns ?

WarC0zes · Juillet 25, 2025, 2:33

Oui, tu ne vois pas les services down ?

djedje · Juillet 25, 2025, 2:34

tout à l’heure non … je recheck

WarC0zes · Juillet 25, 2025, 2:35

Quand j’ai checker, il y avais des services down.

djedje · Juillet 25, 2025, 2:35

www. OK
NS DNS Down
…