histoire de pas faire de bêtises comme d’habitude j’ai besoin d’une aide pour activée l’accès extérieur a mon home assistant …
je suis le tuto de McFly …
.
.
j’ai paramétré ma boxe , nom de domaine perso , et tout et tout …
Mais je bloque là :…
Modification dans l’UI.
ca c’est ok, mais quand je veux
Modification de configuration.yaml.
Dans configuration.yaml et ajouter ceci.
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
.
.
Je fais une vérification dans outils de développement avant de redémarrer , et bim …
.
.
Version core-2024.6.3
Type d'installation Home Assistant OS
Développement false
Supervisor true
Docker true
Utilisateur root
Environnement virtuel false
Version de Python 3.12.2
Famille du système d'exploitation Linux
Version du système d'exploitation 6.6.33-haos
Architecture du processeur x86_64
Fuseau horaire Europe/Paris
Répertoire de configuration /config
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 1391
Downloaded Repositories 5
HACS Data ok
Home Assistant Cloud
Connecté false
Accéder au serveur de certificats ok
Accéder au serveur d'authentification ok
Accéder à Home Assistant Cloud ok
Home Assistant Supervisor
Système d'exploitation hôte Home Assistant OS 12.4
Canal de mise à jour stable
Version du Supervisor supervisor-2024.06.0
Version de l'agent 1.6.0
Version de Docker 26.1.4
Taille total du disque 109.3 GB
Taille du disque utilisé 57.8 GB
Sain true
Prise en charge true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
Tableau de bord generic-x86-64
API du Supervisor ok
Version de l'API ok
Modules complémentaires installés Mosquitto broker (6.4.1), File editor (5.8.0), Zigbee2MQTT (1.38.0-1), Advanced SSH & Web Terminal (18.0.0), Terminal & SSH (9.14.0), Frigate (0.13.2), Studio Code Server (5.15.0), ESPHome (2024.5.5), Samba share (12.3.1), Duck DNS (1.17.0), Let's Encrypt (5.0.18)
Dashboards
Tableaux de bord 2
Ressources 2
Vues 8
Mode storage
Recorder
Heure de démarrage de l'exécution la plus ancienne 12 juin 2024 à 06:26
Heure de démarrage de l'exécution actuelle 20 juin 2024 à 22:19
Taille estimée de la base de données (en Mio) 210.35 MiB
Moteur de la base de données sqlite
Version de la base de données 3.44.2
Métriques du Core
Utilisation du processeur
0.1 %
Utilisation de la mémoire
4.8 %
Métriques du Supervisor
Utilisation du processeur
0 %
Utilisation de la mémoire
1.9 %
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/file-structure.sh
cont-init: info: /etc/cont-init.d/file-structure.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 lets-encrypt (no readiness notification)
s6-rc: info: service legacy-services successfully started
[10:50:37] INFO: Selected http verification
[10:50:37] INFO: Detecting existing certificate type for XXXXXX.freeboxos.fr
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[10:50:38] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Account registered.
Requesting a certificate forXXXXX.freeboxos.fr
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: XXXX.freeboxos.fr
Type: connection
Detail: XXXXXX195: Fetching http:/XXXXfreeboxos.fr/.well-known/acme-challenge/UZXQX-n-znM3X0mxhn3P4WXm_udl0KIlAlCiKJtEjLE: Timeout during connect (likely firewall problem)
Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
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/file-structure.sh
cont-init: info: /etc/cont-init.d/file-structure.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 lets-encrypt (no readiness notification)
s6-rc: info: service legacy-services successfully started
[11:47:26] INFO: Selected http verification
[11:47:26] INFO: Detecting existing certificate type forXXXX.freeboxos.fr
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[11:47:27] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for XXXXXX.freeboxos.fr
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: XXXXXXX.freeboxos.fr
Type: connection
Detail: XXXXX195: Fetching http://XXXXXXeeboxos.fr/.well-known/acme-challenge/BpOTCbGLn0jbpsewYPO-jU1TJTpch7S6y8NJQRplPSg: Timeout during connect (likely firewall problem)
Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Salut @didier02100 alors bien dormi dans un lit moelleux
déjà vérifies, dans les logs de laddon let’encrypt, que les certificats sont bien générés , et je pense que non vu ton erreur de yaml ?
as tu bien ouvert et redirigé les port 443 et 80 vers ta box HA ?
comment on peut faire des connerie !!!
Merci ddfdom, c’est corrigé …
Maintenant vous pouvez entrer cher moi lol !!! y’a l’apéro
On les voie aussi dans ce que tu a copié …