oui c’est la mais les entrées correspondent elles bien a ton ip publique ? (je ne pense pas)
Le A déjà à une adresse IP que je ne connais pas. Je mets celle de mon HA (192.168.185) ?
[Edit] il y a du mieux
http://176.158.126.xx0 qui est l’adresse IP fournie par OVH, me pointe sur cette pagequi est l’adresse IP fournie par OVH, me pointe sur cette page
je pense avoir dit plusiers fois que tu dois vériver quelle est ton ipv4 publique en allant sur monip.org (et pas mon-ip.com)récupère cette ip et colle la dans l’entrée de type A homeassistant.xxxxx.yy
par contre les ip 192.168.x.x sont des ips dites privées ces ips sont injoignables depuis internet
J’ai redémarré le module let’s et NGINX
Sur https://176.158.126.xxx/ j’ai "page échoué
Sur http://176.158.126.xxx 403: Forbidden
Sur https://homeassistant.xxxxx.com et http://homeassistant.xxxxx.com j’ai
Tu lis les posts ou pas ?
Tu as bien viré tes sous domaines dans le manager OVH ?
Et tu as bien ajouté une entrée correspondant à ton ip publique
Désolé je suis complètement perdu je reprend demain
1 « J'aime »
Le problème c’est que la tout ton sous domaine est envoyé sur les serveurs d’ovh et pas chez toi
Ta conf OVH est erronée
La j’ai supprimé le sous-domaine que j’avais crée,on est bien d’accord j’ai fais une boulette?!
Si je supprime de OVH le sous domaine que j’ai créé, comment je peux donc faire pointer ce sous-domaine sur mon HA ? c’est ça que je comprends pas
Alors cela veut dire que je ne me sers plus du sous-domaine OVH ?
c’est de ce sous domaine dont je parlais
c’est avant tout ce qui foutais le bazar
bon on repart de zero
donc dans zonde DNS tu ajoutes une entrée de type A
homeassistant.xxxx.com avec comme destination ton ip publique 176.158.x.x
oui comme là
pour vérifier depuis ton PC que tout est ok au niveau configuration vpn tu tapes la commande nslookup homeassistant.xxxx.com 1.1.1.1 ça doit te retourner ton ip publique 176.158.x.x
Tu peux relancer let’s encrypt afin de créé les certificats
Et poster le log
s6-rc: info: service legacy-services successfully started
[11:35:47] INFO: Selected http verification
[11:35:47] INFO: Detecting existing certificate type for https://homeassistant.xxxxx.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[11:35:54] INFO: No certificate found - using 'ecdsa' key type.
Requested name https://homeassistant.xxxxx.com appears to be a URL, not a FQDN. Try again without the leading "https://".
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-4mlylhjj/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:40:24] INFO: Selected http verification
[11:40:24] INFO: Detecting existing certificate type for homeassistant.xxxxx.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[11:40:25] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for homeassistant.xxxxx.com
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: homeassistant.xxxxx.com
Type: unauthorized
Detail: The key authorization file from the server did not match this challenge. Expected "p22-Gg9RZ46A_DQ-9M2hMvmfAVb9LYYqV4-06Imd3gg.DtYtklcMRwSgadmYzYkhJQbL2ahs1F2nYUHD3rBmpUM" (got "p22-Gg9RZ46A_DQ-9M2hMvmfAVb9LYYqV4-06Imd3gg.4E3VCTFsySjUrqnCg0ooULx-3kbdPBygi0aWkvg5Gd8")
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:57:13] INFO: Selected http verification
[11:57:13] INFO: Detecting existing certificate type for homeassistant.xxxxx.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[11:57:14] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for homeassistant.xxxxx.com
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: homeassistant.xxxxx.com
Type: unauthorized
Detail: The key authorization file from the server did not match this challenge. Expected "y1Q-VfTkD_r-TFwsvWRtlcY9QDzn94KsrGpR8IMn_yo.DtYtklcMRwSgadmYzYkhJQbL2ahs1F2nYUHD3rBmpUM" (got "y1Q-VfTkD_r-TFwsvWRtlcY9QDzn94KsrGpR8IMn_yo.4E3VCTFsySjUrqnCg0ooULx-3kbdPBygi0aWkvg5Gd8")
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
[14:55:20] INFO: Selected http verification
[14:55:20] INFO: Detecting existing certificate type for homeassistant.xxxxx.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[14:55:21] INFO: No certificate found - using 'ecdsa' key type.
Et toujours rien dans SSL
Bon étrange
Tu peux supprimer l’addon let’s encrypt le réinstaller le configurer et relancer la génération du certificat
1 « J'aime »
J’ai donc supprimé et réinstaller let’s
Parameter let’s
Redémarré let’s
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
[14:55:20] INFO: Selected http verification
[14:55:20] INFO: Detecting existing certificate type for homeassistant.hxxxxxx.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[14:55:21] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for homeassistant.handicarauto.com
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: homeassistant.xxxxx.com
Type: unauthorized
Detail: The key authorization file from the server did not match this challenge. Expected "rIFLu-3mf8LB0ZLqjZmoctA1Y2_hzD__juZHxOg0f54.DtYtklcMRwSgadmYzYkhJQbL2ahs1F2nYUHD3rBmpUM" (got "rIFLu-3mf8LB0ZLqjZmoctA1Y2_hzD__juZHxOg0f54.4E3VCTFsySjUrqnCg0ooULx-3kbdPBygi0aWkvg5Gd8")
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
[16:42:23] INFO: Selected http verification
[16:42:23] INFO: Detecting existing certificate type for homeassistant.xxxxxo.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[16:42:24] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Account registered.
Requesting a certificate for homeassistant.hxxxxx.com
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: homeassistant.xxxxxx.com
Type: unauthorized
Detail: The key authorization file from the server did not match this challenge. Expected "VA5A-TSw8y2SNEHDUtyK_leLYAP-xzE5n0mkNKVhf-g.eTjpfzlqOF0OrGpaUgtZbDssZdLnjhpmnH6AQNSYweE" (got "VA5A-TSw8y2SNEHDUtyK_leLYAP-xzE5n0mkNKVhf-g.4E3VCTFsySjUrqnCg0ooULx-3kbdPBygi0aWkvg5Gd8")
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
[16:45:40] INFO: Selected http verification
[16:45:40] INFO: Detecting existing certificate type for homeassistant.xxxxxx.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[16:45:41] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for homeassistant.xxxxxx.com
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: homeassistant.xxxxxxx.com
Type: unauthorized
Detail: The key authorization file from the server did not match this challenge. Expected "1-lzvk2mtJAatNf5nHm-8WuPmT6LGEkgQKod5nXT2Cg.eTjpfzlqOF0OrGpaUgtZbDssZdLnjhpmnH6AQNSYweE" (got "1-lzvk2mtJAatNf5nHm-8WuPmT6LGEkgQKod5nXT2Cg.4E3VCTFsySjUrqnCg0ooULx-3kbdPBygi0aWkvg5Gd8")
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
toujours riens le ssl
[EDIT]
Je viens d’en faire un test tout bête. Je viens d’installer un Home Assistant sur un autre ordinateur avec une machine virtuelle UTM. J’ai également installé le module let’s puis configurer, puis lancer. Dans le dossier SSL, il n’y a aucun dossier. De plus, voici les logs généré après le lancement de Let’s
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
[17:50:24] INFO: Selected http verification
[17:50:24] INFO: Detecting existing certificate type for homeassistant.xxxxx.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[17:50:26] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Account registered.
Requesting a certificate for homeassistant.xxxxx.com
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: homeassistant.xxxxx.com
Type: unauthorized
Detail: The key authorization file from the server did not match this challenge. Expected "gS7XavVVqQA9cEPwe75lk1j-y39q2pO1N5Qi13DOqcI.l39oMjhrM5MwStKJLVaaGaB76tPc4TVnseyNerhDTtI" (got "gS7XavVVqQA9cEPwe75lk1j-y39q2pO1N5Qi13DOqcI.4E3VCTFsySjUrqnCg0ooULx-3kbdPBygi0aWkvg5Gd8")
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
C’est pas un problème de machine, mais du port 80 qui n’est pas ouvert pour Home assistant.
Tu devais retester avec le challenge DNS, qui n’as pas besoin du port 80.
Comme ta configuration sur OVH doit être OK, ça devrait passer c’est fois.
je ne sais pas alors, ça dépasse mes compétences. Voir si @ddfdom @anon21985933 aurais une idée.
C’est ton dns, pas ton IP de HA 
Oui et voici le résultat
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
[16:45:40] INFO: Selected http verification
[16:45:40] INFO: Detecting existing certificate type for homeassistant.monsite.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[16:45:41] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for homeassistant.monsite.com
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: homeassistant.monsite.com
Type: unauthorized
Detail: The key authorization file from the server did not match this challenge. Expected "1-lzvk2mtJAatNf5nHm-8WuPmT6LGEkgQKod5nXT2Cg.eTjpfzlqOF0OrGpaUgtZbDssZdLnjhpmnH6AQNSYweE" (got "1-lzvk2mtJAatNf5nHm-8WuPmT6LGEkgQKod5nXT2Cg.4E3VCTFsySjUrqnCg0ooULx-3kbdPBygi0aWkvg5Gd8")
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
[18:11:52] INFO: Selected http verification
[18:11:52] INFO: Detecting existing certificate type for homeassistant.monsite.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[18:11:53] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for homeassistant.monsite.com
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: homeassistant.monsite.com
Type: unauthorized
Detail: The key authorization file from the server did not match this challenge. Expected "L7ZvWFYQ8Ymsk_TmSHxwKQlrPQgxuvv23rH6k9u3WRo.eTjpfzlqOF0OrGpaUgtZbDssZdLnjhpmnH6AQNSYweE" (got "L7ZvWFYQ8Ymsk_TmSHxwKQlrPQgxuvv23rH6k9u3WRo.4E3VCTFsySjUrqnCg0ooULx-3kbdPBygi0aWkvg5Gd8")
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
[19:33:54] INFO: Selected DNS Provider: null
[19:33:54] INFO: Use propagation seconds: 60
[19:33:54] INFO: Detecting existing certificate type for homeassistant.monsite.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[19:33:55] INFO: No certificate found - using 'ecdsa' key type.
usage:
certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...
Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,
it will attempt to use a webserver both for obtaining and installing the
certificate.
certbot: error: unrecognized arguments: --null --null-credentials /data/dnsapikey
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