Using the Nginx proxy we can avoid all this by offloading HTTPS termination to Nginx, leaving Home Assistant open to serve local requests from Konnected over fast unencrypted HTTP.
These certificates require significant memory & processing power to negotiate, which causes severe performance and reliability issues on Konnected's tiny ESP8266 chip. This is problematic for the Konnected devices when used with the LetsEncrypt certificates generated by the DuckDNS addon. Currently the http component can't serve both HTTP and HTTPS at the same time, so if this is enabled, all API traffic to Home Assistant must be over HTTPS. Without the Nginx Proxy, Home Assistant itself is responsible for serving your SSL/TLS certificates via the http component.
The easiest and most popular way to do this is using Hass.io with the DuckDNS and NGINX Proxy add-ons. To be able to access your Home Assistant dashboard securely from outside your home, you need to set up a dynamic DNS provider, SSL/TLS certificates, and a path to access your Home Assistant instance from outside your network.
0 kommentar(er)
