Bonjour
Mon problème
J’utilise actuellement un domaine duckdns avec l’option let’s encrypt pour le chiffrement SSL.
Afin de pouvoir utiliser l’adresse locale depuis l’application mobile HA, je souhaiterai migrer vers la solution reverse proxy de NGINX.
J’ai suivi ce tuto:
https://forum.hacf.fr/t/acces-de-l-exterieur-en-https-avec-nginx-proxy-manager/1761
Mais j’obtiens une erreur lors de la création du certificat: (internal error sur l’IHM)
Voici la log:
[6/8/2022] [2:03:13 PM] [Nginx ] › ℹ info Reloading Nginx
[6/8/2022] [2:03:14 PM] [SSL ] › ℹ info Requesting Let'sEncrypt certificates for Cert #7: toto.duckdns.org
[6/8/2022] [2:03:31 PM] [Nginx ] › ℹ info Reloading Nginx
[6/8/2022] [2:03:31 PM] [Express ] › ⚠ warning Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-7" --agree-tos --email "toto@gmail.com" --preferred-challenges "dns,http" --domains "toto.duckdns.org"
Saving debug log to /data/logs/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Performing the following challenges:
http-01 challenge for toto.duckdns.org
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.
Waiting for verification...
Challenge failed for domain toto.duckdns.org
http-01 challenge for toto.duckdns.org
Cleaning up challenges
Some challenges have failed.
J’ai essayé en arretant le module « Duckdns » et en supprimant les certificats mais l’erreur est toujours présente.
Ma configuration
System Health
| version |
core-2022.6.3 |
| installation_type |
Home Assistant OS |
| dev |
false |
| hassio |
true |
| docker |
true |
| user |
root |
| virtualenv |
false |
| python_version |
3.9.12 |
| os_name |
Linux |
| os_version |
5.15.32-v8 |
| arch |
aarch64 |
| timezone |
Europe/Paris |
Home Assistant Community Store
| GitHub API |
ok |
| GitHub Content |
ok |
| GitHub Web |
ok |
| GitHub API Calls Remaining |
4732 |
| Installed Version |
1.25.5 |
| Stage |
running |
| Available Repositories |
1060 |
| Downloaded Repositories |
41 |
Home Assistant Cloud
| logged_in |
false |
| can_reach_cert_server |
ok |
| can_reach_cloud_auth |
ok |
| can_reach_cloud |
ok |
Home Assistant Supervisor
| host_os |
Home Assistant OS 8.1 |
| update_channel |
stable |
| supervisor_version |
supervisor-2022.05.3 |
| agent_version |
1.2.1 |
| docker_version |
20.10.14 |
| disk_total |
58.9 GB |
| disk_used |
27.8 GB |
| healthy |
true |
| supported |
true |
| board |
rpi4-64 |
| supervisor_api |
ok |
| version_api |
ok |
| installed_addons |
Samba share (9.6.1), File editor (5.3.3), Duck DNS (1.15.0), deCONZ (6.14.1), Terminal & SSH (9.4.0), Node-RED (12.0.0), Mosquitto broker (6.1.2), Check Home Assistant configuration (3.10.0), InfluxDB (4.4.1), Grafana (7.5.2), Glances (0.15.0), SSH & Web Terminal (11.0.0), Log Viewer (0.13.0), ESPHome (2022.3.1), NGINX Home Assistant SSL proxy (3.1.1), Zigbee2mqtt (1.25.2-1), Home Assistant Google Drive Backup (0.108.2), Enedisgateway2mqtt (0.7.7-3), Studio Code Server (5.0.6), Zigbee2mqtt Edge (edge), Nginx Proxy Manager (0.11.0), MariaDB (2.4.0) |
Dashboards
| dashboards |
2 |
| resources |
27 |
| views |
10 |
| mode |
storage |
Recorder
| oldest_recorder_run |
2 juin 2022, 07:11 |
| current_recorder_run |
8 juin 2022, 14:00 |
| estimated_db_size |
722.10 MiB |
| database_engine |
sqlite |
| database_version |
3.34.1 |
___
Bon finalement, je n’ai peut-être pas attendu assez longtemps mais la suppression de mes anciens certificats SSL a résolu le problème. 
1 « J'aime »