From 7e96257c93b55b00a99cb241363a138cec71d0d0 Mon Sep 17 00:00:00 2001
From: jolzem <jolzem@pm.me>
Date: Sun, 10 Nov 2024 17:43:19 +0100
Subject: [PATCH] Added 400 Bad Request error to HomeAssistant quick fix

---
 blog/quick-fixes/homeassistant-proxy/index.html | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/blog/quick-fixes/homeassistant-proxy/index.html b/blog/quick-fixes/homeassistant-proxy/index.html
index c2856e5..ac9c539 100755
--- a/blog/quick-fixes/homeassistant-proxy/index.html
+++ b/blog/quick-fixes/homeassistant-proxy/index.html
@@ -24,11 +24,21 @@
     <h1>HomeAssistant not connecting over reverse proxy</h1>
     <br>
     <p>
-      Make sure you have enabled <em>Websockets Supports</em> or similar functionality in your reverse proxy client.
+      Make sure you have enabled <em>Websockets Supports</em> or similar functionality in your reverse proxy client.<br><br>
+      If you are getting a <em>400 Bad Request</em> error, find the HomeAssistant log file and look for the following error message:<br>
+      <code>A request from a reverse proxy was received from 12.34.56.78, but your HTTP integration is not set-up for reverse proxies</code><br><br>
+      In your <code>configuration.yaml</code> file, add the following lines:<br>
+      <pre style="text-align:left;">
+http:<br>
+  use_x_forwarded_for: true<br>
+  trusted_proxies:<br>
+    - 12.34.56.78 # The IP address from the error message
+</pre>
     </p>
     <h2>Explanation</h2>
     <p>
-      HomeAssistant uses websockets to communicate with the browser.
+      HomeAssistant uses websockets to communicate with the browser.<br><br>
+      If you are using a reverse proxy, the IP address of the incoming connection is not trusted and gets rejected by HomeAssistant.<br>
     </p>
   </main>
   <footer>