Accès duckdns+application homeassistant

Bonjour ddfdom,
désolé pour ma réponse tardive.
j’ai récupéré et je me connecte à l’adresse locale.
Duck dns j’ai le log

[17:19:37] INFO: Renew certificate for domains: ****.duckdns.org and aliases: 
# INFO: Using main config file /data/workdir/config
Processing ****.duckdns.org
 + Checking domain name(s) of existing cert... changed!
 + Domain name(s) are not matching!
 + Names in old certificate: ****.duckdns.org lucbobeleyn.duckdns.org
 + Configured names: ****.duckdns.org
 + Forcing renew.
 + Checking expire date of existing cert...
 + Valid till Jul  3 04:18:33 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 1 authorizations URLs from the CA
 + Handling authorization for ****.duckdns.org
 + Found valid authorization for ****.duckdns.org
 + 0 pending challenge(s)
 + Requesting certificate...
Warning: Will read cert request from stdin since no -in option is given
 + Checking certificate...
 + Done!
 + Creating fullchain.pem...
 + Done!

ce qui me parait plutôt de bonne augure.

NGINX j’ai

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 nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service crond: starting
s6-rc: info: service crond successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[16:58:17] INFO: Merging options & variables for template
[16:58:35] INFO: Generating nginx.conf from template in /etc/nginx/nginx.conf.gtpl
[16:58:37] INFO: Generating dhparams (this will take some time)...
Generating DSA parameters, 4096 bit long prime
.....+.............+.+.+...+....+....+..+........+.+.....+.....+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*
...+..+..+..+.............+.....+...+..........+......+...............+......+..+........+...+........+..................+......+.....+.........+.................+........+.+...+..+.........+.....+..+.+.................+...+......+........................+........+...+.+..+............+..........+..+..+......+...........+.....+...+....+......+..........+........+.......................................+........+.............+...........+..............+..........+...+...........+..+....+....+....+.+.....+......................+..+.......+..........................+..+.....+.......+.+......+....+......+.........................+......+.+..+....+.........................+...+............+...+.+.+.......+...........+...........+...+.........+..+.......+.................+....+................+........+......+.+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*
[16:59:41] INFO: Running nginx...

là aussi ça me paraît pas mal
Ma box c’est peut être mon erreur :
image
pour l’instant je n’ai pas ajouté à configuration.yaml

http:
#  ssl_certificate: /ssl/fullchain.pem
#  ssl_key: /ssl/privkey.pem
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.0/24

parce que si je le fait (sans redémarrer pour pas me faire b***er de nouveau) je n’arrive pas à me connecter, ni https ni http