Accès duckdns+application homeassistant

ddfdom · Avril 1, 2025, 6:47

C’est pas les lignes home assistant qu’il faut mais les logs de l’addon

La dernière fois il te manquais les certificats
Car ils n’étaient pas générées par l’addon duckdns ?
Sont ils générés maintenant ? Où sont les logs ?

lubobel · Avril 1, 2025, 6:56

euh je sais pas trop, je dirais que la fin du log de duckdns montre qu’il y a un problème Challenge validation has failed :( ERROR: Challenge is invalid! (returned: invalid) (result: ["type"] "dns-01" ["url"] "https://
je vais essayer de suivre la vidéo envoyée par tochy

lubobel · Avril 1, 2025, 7:34

j’ai ajouté un tiret dans mon adresse duck dns, j’ai une erreur de certificat sur chrome en navigation privée mais nginx est démarré


[21:25:08] INFO: Merging options & variables for template

[21:25:09] INFO: Generating nginx.conf from template in /etc/nginx/nginx.conf.gtpl

[21:25:09] INFO: Running nginx...

Votre connexion n'est pas privée
Des pirates informatiques tentent peut-être de voler vos informations sur ***-*****.duckdns.org (mots de passe, messages ou cartes de crédit, par exemple). En savoir plus sur cet avertissement
net::ERR_CERT_INVALID
Un chiffrement est normalement utilisé sur le site ***-***.duckdns.org pour protéger vos informations. Lors de la dernière tentative de connexion de Chrome au site ***-*****.duckdns.org, des identifiants inhabituels et incorrects ont été retournés. Il est possible qu'un individu malveillant tente de se faire passer pour ***-******.duckdns.org ou qu'un écran de connexion Wi-Fi ait interrompu la connexion. Vos informations restent sécurisées, car nous avons arrêté la connexion avant l'échange des données.

Vous ne pouvez pas consulter le site ***-*****.duckdns.org pour le moment, car il a envoyé des identifiants brouillés qui ne peuvent être traités par Chrome. Les erreurs réseau et les attaques sont généralement temporaires. Vous devriez donc pouvoir accéder à cette page ultérieurement.

ddfdom · Avril 1, 2025, 7:53

Fait une capture de ta configuration de duckdns ennczcha’t la aprie sensible de ton nom de domaine

Il faut mettre juste le nom de domaine pas de http pas de port juste le nom de domaine
mondomaine.duckdns.org

lubobel · Avril 1, 2025, 8:00

bah là c’est la merde! en local je ping l’adresse mais 192.168.1.10 ça ne marche plus aucune donnée.
j’ai décommenté les lignes ssl-certificate et ssl_key avant de rédémarrer

ddfdom · Avril 1, 2025, 8:04

Si tu utilises le reverse proxy nginx ssl il le faut pas ajouter les certificats dans le configuration.yaml

Je pense que tu mélange tout

Il faut configurer l’addon duckdns vérifier que les certificats sont bien générés dans /ssl
Puis configurer nginx ssl m, ajouter les lignes pour autoriser le reverse proxy
Configurer ton routeur/box et rediriger le port 443 vers l’IP de HA

lubobel · Avril 1, 2025, 8:10

je pense aussi que je mélange tout, je suis hors de mon domaine et j’essaie mais je galère. Là ma solution c’est de reformater ma sd et de remettre une sauvegarde qui est sur google drive mais demain

ddfdom · Avril 1, 2025, 8:13

Tu as essayé avec https devant ton ip

C’est pas faute de te demander des captures des logs pour t’aider …

lubobel · Avril 1, 2025, 8:18

j’ai essayé (à l’instant et sans succès). Je ne remet pas en question l’aide que vous apportez (et la patience dont vous faites preuve), la capture des logs je comprend ce que ça veut dire, vérifier que les certifs sont générés dans /ssl j’avoue que je ne suis pas sur, ça a l’air simple pour vous

ddfdom · Avril 1, 2025, 8:21

Tu n’imagines pas comme c’est simple
En fait lorsque l’addon duckdns genere le certificat il crée 2 fichiers dans le répertoire /ssl

Si tu as modifié le fichier configuration.yaml, si tu as installé samba share tu peux le modifier via ton pc car je pense que c’est lui qui doit bloquer

Tjs a vérifier la cohérence de ce fichier avant de redémarrer

lubobel · Avril 1, 2025, 8:56

ce n’est pas si simple pour moi, je ne parvient même pas à remettre une image fonctionnelle

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
cont-init: info: running /etc/cont-init.d/udev.sh
[20:48:34] INFO: Using udev information from host
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
s6-rc: info: service legacy-services successfully started
[20:48:35] INFO: Starting local supervisor watchdog...
2025-04-01 20:48:42.745 INFO (MainThread) [__main__] Initializing Supervisor setup
2025-04-01 20:48:43.034 INFO (MainThread) [supervisor.coresys] Setting up coresys for machine: raspberrypi3-64
2025-04-01 22:48:43.058 INFO (MainThread) [supervisor.docker.supervisor] Attaching to Supervisor ghcr.io/home-assistant/aarch64-hassio-supervisor with version 2025.03.4
2025-04-01 22:48:43.058 INFO (MainThread) [supervisor.docker.supervisor] Connecting Supervisor to hassio-network
2025-04-01 22:48:43.429 INFO (SyncWorker_0) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/aarch64-hassio-supervisor:2024.05.1']
2025-04-01 22:48:45.554 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state initialize
2025-04-01 22:48:45.566 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-04-01 22:48:45.568 INFO (MainThread) [__main__] Setting up Supervisor
2025-04-01 22:48:45.760 INFO (MainThread) [supervisor.api] Starting API on 172.30.32.2
2025-04-01 22:48:46.007 INFO (MainThread) [supervisor.hardware.monitor] Started Supervisor hardware monitor
2025-04-01 22:48:46.020 INFO (MainThread) [supervisor.dbus.manager] Connected to system D-Bus.
2025-04-01 22:48:46.022 INFO (MainThread) [supervisor.dbus.agent] Load dbus interface io.hass.os
2025-04-01 22:48:46.025 INFO (MainThread) [supervisor.dbus.hostname] Load dbus interface org.freedesktop.hostname1
2025-04-01 22:48:46.028 INFO (MainThread) [supervisor.dbus.logind] Load dbus interface org.freedesktop.login1
2025-04-01 22:48:46.032 INFO (MainThread) [supervisor.dbus.network] Load dbus interface org.freedesktop.NetworkManager
2025-04-01 22:48:46.036 INFO (MainThread) [supervisor.dbus.rauc] Load dbus interface de.pengutronix.rauc
2025-04-01 22:48:46.038 INFO (MainThread) [supervisor.dbus.resolved] Load dbus interface org.freedesktop.resolve1
2025-04-01 22:48:46.040 INFO (MainThread) [supervisor.dbus.systemd] Load dbus interface org.freedesktop.systemd1
2025-04-01 22:48:46.041 INFO (MainThread) [supervisor.dbus.timedate] Load dbus interface org.freedesktop.timedate1
2025-04-01 22:48:46.304 ERROR (MainThread) [supervisor.dbus.agent] Can't load OS Agent dbus interface io.hass.os /io/hass/os/Config/Swap: D-Bus object /io/hass/os/Config/Swap is not usable, introspection is missing required properties interface
2025-04-01 22:48:47.170 INFO (MainThread) [supervisor.host.services] Updating service information
2025-04-01 22:48:47.193 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
2025-04-01 22:48:47.574 INFO (MainThread) [supervisor.host.network] Updating local network information
2025-04-01 22:48:47.816 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}
2025-04-01 22:48:47.867 INFO (MainThread) [supervisor.docker.monitor] Started docker events monitor
2025-04-01 22:48:47.869 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
2025-04-01 22:48:48.212 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-cli with version 2024.05.0
2025-04-01 22:48:48.317 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-dns with version 2024.04.0
2025-04-01 22:48:48.374 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
2025-04-01 22:48:48.423 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-audio with version 2023.12.0
2025-04-01 22:48:48.488 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-observer with version 2023.06.0
2025-04-01 22:48:48.553 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-multicast with version 2024.03.0
2025-04-01 22:48:48.605 INFO (MainThread) [supervisor.plugins.manager] Plugin cli is not up-to-date, latest version 2025.02.0, updating
2025-04-01 22:48:48.613 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/aarch64-hassio-cli:2024.05.0 to ghcr.io/home-assistant/aarch64-hassio-cli:2025.02.0
2025-04-01 22:48:48.614 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/aarch64-hassio-cli with tag 2025.02.0.
2025-04-01 22:48:51.935 INFO (SyncWorker_3) [supervisor.docker.manager] Stopping hassio_cli application
2025-04-01 22:48:56.060 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning hassio_cli application
2025-04-01 22:48:56.274 INFO (SyncWorker_4) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/aarch64-hassio-cli:2024.05.0']
2025-04-01 22:48:56.386 INFO (MainThread) [supervisor.plugins.cli] Starting CLI plugin
2025-04-01 22:48:57.653 INFO (MainThread) [supervisor.docker.cli] Starting CLI ghcr.io/home-assistant/aarch64-hassio-cli with version 2025.02.0 - 172.30.32.5
2025-04-01 22:48:57.656 INFO (MainThread) [supervisor.plugins.manager] Plugin dns is not up-to-date, latest version 2025.02.0, updating
2025-04-01 22:48:57.668 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/aarch64-hassio-dns:2024.04.0 to ghcr.io/home-assistant/aarch64-hassio-dns:2025.02.0
2025-04-01 22:48:57.669 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/aarch64-hassio-dns with tag 2025.02.0.
2025-04-01 22:49:03.762 INFO (SyncWorker_2) [supervisor.docker.manager] Stopping hassio_dns application
2025-04-01 22:49:08.937 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning hassio_dns application
2025-04-01 22:49:09.119 INFO (SyncWorker_1) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/aarch64-hassio-dns:2024.04.0']
2025-04-01 22:49:09.664 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
2025-04-01 22:49:10.881 INFO (MainThread) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/aarch64-hassio-dns with version 2025.02.0 - 172.30.32.3
2025-04-01 22:49:10.885 INFO (MainThread) [supervisor.plugins.manager] Plugin audio is not up-to-date, latest version 2025.02.0, updating
2025-04-01 22:49:10.897 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/aarch64-hassio-audio:2023.12.0 to ghcr.io/home-assistant/aarch64-hassio-audio:2025.02.0
2025-04-01 22:49:10.898 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/aarch64-hassio-audio with tag 2025.02.0.
2025-04-01 22:49:21.977 INFO (SyncWorker_0) [supervisor.docker.manager] Stopping hassio_audio application
2025-04-01 22:49:28.157 INFO (SyncWorker_0) [supervisor.docker.manager] Cleaning hassio_audio application
2025-04-01 22:49:28.365 INFO (SyncWorker_3) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/aarch64-hassio-audio:2023.12.0']
2025-04-01 22:49:29.327 INFO (MainThread) [supervisor.plugins.audio] Starting Audio plugin
2025-04-01 22:49:30.697 INFO (MainThread) [supervisor.docker.audio] Starting Audio ghcr.io/home-assistant/aarch64-hassio-audio with version 2025.02.0 - 172.30.32.4
2025-04-01 22:49:30.701 INFO (MainThread) [supervisor.plugins.manager] Plugin observer is not up-to-date, latest version 2025.02.0, updating
2025-04-01 22:49:30.714 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/aarch64-hassio-observer:2023.06.0 to ghcr.io/home-assistant/aarch64-hassio-observer:2025.02.0
2025-04-01 22:49:30.715 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/aarch64-hassio-observer with tag 2025.02.0.
2025-04-01 22:49:33.925 INFO (SyncWorker_4) [supervisor.docker.manager] Stopping hassio_observer application
2025-04-01 22:49:35.198 INFO (SyncWorker_4) [supervisor.docker.manager] Cleaning hassio_observer application
2025-04-01 22:49:35.359 INFO (SyncWorker_3) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/aarch64-hassio-observer:2023.06.0']
2025-04-01 22:49:35.438 INFO (MainThread) [supervisor.plugins.observer] Starting observer plugin
2025-04-01 22:49:36.800 INFO (MainThread) [supervisor.docker.observer] Starting Observer ghcr.io/home-assistant/aarch64-hassio-observer with version 2025.02.0 - 172.30.32.6
2025-04-01 22:49:36.803 INFO (MainThread) [supervisor.plugins.manager] Plugin multicast is not up-to-date, latest version 2025.02.0, updating
2025-04-01 22:49:36.813 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/aarch64-hassio-multicast:2024.03.0 to ghcr.io/home-assistant/aarch64-hassio-multicast:2025.02.0
2025-04-01 22:49:36.814 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/aarch64-hassio-multicast with tag 2025.02.0.
2025-04-01 22:49:38.610 INFO (SyncWorker_0) [supervisor.docker.manager] Stopping hassio_multicast application
2025-04-01 22:49:42.416 INFO (SyncWorker_0) [supervisor.docker.manager] Cleaning hassio_multicast application
2025-04-01 22:49:42.595 INFO (SyncWorker_2) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/aarch64-hassio-multicast:2024.03.0']
2025-04-01 22:49:43.150 INFO (MainThread) [supervisor.plugins.multicast] Starting Multicast plugin
2025-04-01 22:49:43.951 INFO (MainThread) [supervisor.docker.multicast] Starting Multicast ghcr.io/home-assistant/aarch64-hassio-multicast with version 2025.02.0 - Host
2025-04-01 22:49:43.964 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 0 Home Assistant secrets
2025-04-01 22:49:43.977 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/raspberrypi3-64-homeassistant with version landingpage
2025-04-01 22:49:44.023 INFO (MainThread) [supervisor.homeassistant.core] Starting HomeAssistant landingpage
2025-04-01 22:49:44.158 INFO (MainThread) [supervisor.os.manager] Detect Home Assistant Operating System 12.3 / BootSlot A
2025-04-01 22:49:44.171 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/a0d7b954 repository
2025-04-01 22:49:44.172 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/5c53de3b repository
2025-04-01 22:49:44.174 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/core repository
2025-04-01 22:49:44.192 INFO (MainThread) [supervisor.store.git] Cloning add-on /data/addons/git/d5369777 repository from https://github.com/music-assistant/home-assistant-addon
2025-04-01 22:49:46.747 INFO (MainThread) [supervisor.store] Loading add-ons from store: 82 all - 82 new - 0 remove
2025-04-01 22:49:46.885 INFO (MainThread) [supervisor.addons.manager] Found 0 installed add-ons
2025-04-01 22:49:47.994 INFO (MainThread) [supervisor.backups.manager] Found 0 backup files
2025-04-01 22:49:47.995 INFO (MainThread) [supervisor.discovery] Loaded 0 messages
2025-04-01 22:49:47.995 INFO (MainThread) [supervisor.ingress] Loaded 0 ingress sessions
2025-04-01 22:49:47.995 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state setup
2025-04-01 22:49:47.996 INFO (MainThread) [supervisor.resolution.checks.base] Run check for detached_addon_missing/addon
2025-04-01 22:49:47.996 INFO (MainThread) [supervisor.resolution.checks.base] Run check for detached_addon_removed/addon
2025-04-01 22:49:47.996 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disabled_data_disk/system
2025-04-01 22:49:47.997 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2025-04-01 22:49:47.998 INFO (MainThread) [supervisor.resolution.check] System checks complete
2025-04-01 22:49:47.998 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state setup
2025-04-01 22:49:47.999 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-04-01 22:49:47.001 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not running - setup
2025-04-01 22:49:47.002 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state setup
2025-04-01 22:49:47.003 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-04-01 22:49:47.006 INFO (MainThread) [__main__] Running Supervisor
2025-04-01 22:49:47.099 INFO (MainThread) [supervisor.os.manager] Rauc: slot A - activated slot kernel.0, marked slot kernel.0 as good
2025-04-01 22:49:47.148 INFO (MainThread) [supervisor.addons.manager] Phase 'initialize' starting 0 add-ons
2025-04-01 22:49:47.186 INFO (MainThread) [supervisor.addons.manager] Phase 'system' starting 0 add-ons
2025-04-01 22:49:47.186 INFO (MainThread) [supervisor.addons.manager] Phase 'services' starting 0 add-ons
2025-04-01 22:49:47.202 INFO (MainThread) [supervisor.core] Skipping start of Home Assistant
2025-04-01 22:49:47.203 INFO (MainThread) [supervisor.addons.manager] Phase 'application' starting 0 add-ons
2025-04-01 22:49:47.225 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
2025-04-01 22:49:47.227 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant setup
2025-04-01 22:49:47.228 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/raspberrypi3-64-homeassistant:landingpage to ghcr.io/home-assistant/raspberrypi3-64-homeassistant:2025.3.4
2025-04-01 22:49:47.229 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/raspberrypi3-64-homeassistant with tag 2025.3.4.
2025-04-01 22:49:47.230 INFO (MainThread) [supervisor.host.info] Updating local host information
2025-04-01 22:49:47.237 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
2025-04-01 22:49:47.253 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
2025-04-01 22:49:47.254 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
2025-04-01 22:49:47.274 INFO (MainThread) [supervisor.core] Supervisor is up and running
2025-04-01 22:49:47.296 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
2025-04-01 22:49:47.297 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
2025-04-01 22:49:47.307 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disabled_data_disk/system
2025-04-01 22:49:47.309 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
2025-04-01 22:49:47.310 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
2025-04-01 22:49:47.311 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
2025-04-01 22:49:47.357 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
2025-04-01 22:49:47.380 INFO (MainThread) [supervisor.resolution.checks.base] Run check for no_current_backup/system
2025-04-01 22:49:47.380 INFO (MainThread) [supervisor.resolution.module] Create new suggestion create_full_backup - system / None
2025-04-01 22:49:47.381 INFO (MainThread) [supervisor.resolution.module] Create new issue no_current_backup - system / None
2025-04-01 22:49:47.382 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
2025-04-01 22:49:47.392 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2025-04-01 22:49:47.393 INFO (MainThread) [supervisor.resolution.check] System checks complete
2025-04-01 22:49:47.394 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2025-04-01 22:49:47.923 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-04-01 22:49:47.924 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2025-04-01 22:49:47.925 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2025-04-01 22:49:48.813 INFO (MainThread) [supervisor.host.services] Updating service information
2025-04-01 22:49:48.842 INFO (MainThread) [supervisor.host.network] Updating local network information
2025-04-01 22:49:49.756 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
2025-04-01 22:49:49.815 INFO (MainThread) [supervisor.host.manager] Host information reload completed

ddfdom · Avril 1, 2025, 9:18

Tu as récupéré ton home assistant ?

Et tu arrives à te connecter sur le supervisor ?
Il est joignable sur le port 4357

lubobel · Avril 4, 2025, 3:31

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 :

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

WarC0zes · Avril 4, 2025, 3:33

plus besoin du 8123 vers 8123.
C’est 443 vers 443.

ddfdom · Avril 4, 2025, 3:36

Effectivement dans ta box ça ne vas pas il faut rediriger le port 443 vers l’IP de home assistant

Il faut bien modifier ton configuration.yaml pour y ajouter ces lignes

http:
  use_x_forwarded_for: true
  trusted_proxies:
     - 172.30.33.0/24

Et surtout il faut utiliser dans outils de développement la validation du fichier yaml pour être sûr de sa syntaxe

lubobel · Avril 4, 2025, 3:55

j’ai tellement peur de redémarrer, si je dois tout remettre c’est moi qui ne m’en remettrait pas!

j’ai ajouté les lignes

dans configuration.yaml allez alea jacta est, je redémarre HA

lubobel · Avril 4, 2025, 4:03

Ca y est, merci à vous et particulièrement à ddfdom pour sa réactivité et ses conseils, je sais que je n’ai pas été très bon, c’était clairement ma redirection de port qui était erronée.

WarC0zes · Avril 4, 2025, 4:10

Pourtant c’est ce que je t’es dit dans le premier message…

Merci @ddfdom

lubobel · Avril 8, 2025, 11:46

merci à toi aussi @WarC0zes

WarC0zes · Avril 8, 2025, 1:01

Pense à mettre ton sujet en résolu en cochant la case solution sur le message qui l’apporte.