Yes we have the opportunity to follow the existing documentation to setup remote access with https , this is anyway a good exercice.
What the documentation says about the use of Duckns and Letencrypt addon and https
1) From “Remote access page”
https://www.home-assistant.io/docs/configuration/remote/
- propose Duckdns for a free dynnamic DDNS
- then propose Letsencrypt https:
1a) https://www.home-assistant.io/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/
Or
1b) Installing TLS/SSL using Let's Encrypt
2) from “Effortless encryption with Let’s Encrypt and DuckDNS” page
- automatic generation and updating of Let’s Encrypt certificates for your DuckDNS domain
- Use of https = OK
- configuration of http in configuration.yaml = The problem described in this topic
- Http challenge is setup in my system
For non hassio system https://www.splitbrain.org/blog/2017-08/10-homeassistant_duckdns_letsencrypt
3) from “HASS, DuckDNS and Let’s Encrypt” blog page
NOT DONE
Conclusion :In my HA supervised system , i have installed as per the documentation above :
- Duckdns addon : point1a)
- Letsencrypt addon + http challenge: point2)
But I stopped here ( https local+remote OK) , I haved not done point3) so my questions :
Let’s review and confirm that the documentation above is sufficient and correct for point 1) , 2), 3) , for the benefit of every new user ( and me for Supervised install)
Thank you