From ea4da0cba2c2981d59ff48f3a9de762464bc5a7a Mon Sep 17 00:00:00 2001 From: KD Puvvadi Date: Tue, 6 Aug 2024 09:37:38 +0530 Subject: [PATCH] Update 2023-09-29-home-assistant-reverse-proxy-traefik.md --- _posts/2023-09-29-home-assistant-reverse-proxy-traefik.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_posts/2023-09-29-home-assistant-reverse-proxy-traefik.md b/_posts/2023-09-29-home-assistant-reverse-proxy-traefik.md index e259a2c..e42aced 100644 --- a/_posts/2023-09-29-home-assistant-reverse-proxy-traefik.md +++ b/_posts/2023-09-29-home-assistant-reverse-proxy-traefik.md @@ -100,13 +100,13 @@ http: ``` {: file="traefik/data/config/hass.yml" } -Make necessary changes such as `url`, `ip` of the `Home Assistant` and `ipWhiteList` according to your network. Headers are curtesy of [Techno Time](https://technotim.live/). +Make necessary changes such as `url`, `ip` of the `Home Assistant` and `ipWhiteList` according to your network. Headers are curtesy of [Techno Tim](https://technotim.live/). home assistant will be available are the given url e.g. `hass.example.net`. But hass throws `Bad Request` error. Reason being it only allows reverse proxying from whitelisted ip ranges. ### configuration -Add following `http` config to `configuration.yaml` +Add following `http` config to Home Assistant's `configuration.yaml` ```yaml http: @@ -120,7 +120,7 @@ http: Please add required networks and docker network both to the `trusted_proxies` and restart the hass instance. -After few minutes `Home Assistant` will be available at `https:?/hass.example.net`. +After few minutes `Home Assistant` will be available at `https://hass.example.net`. ## Conclusion