Suppose you have already used my Synology Wildcard guide to get Home Assistant to work over HTTPS. And today, following the latest Home Assistant update, you’ve found that you can no longer get Reverse Proxy for Home Assistant to work. If you are getting a 400: Bad Request error when you try to access your Home Assistant via HTTPS, then you’re not alone. In today’s article I will teach you how to fix the Home Assistant error and access your Home Assistant over a secure HTTPS connection again!

Note: Check out my new guide on How to Fix 400: Bad Request error on Home Assistant Supervisor

• STEP 1

Please Support My work by Making a Donation.

• STEP 2

Open Docker package. Go to Network then bridge. Copy your Gateway IP. In my case 172.17.0.1 Follow the instructions in the image below.

• STEP 3

Install the Text Editor Package. Skip this STEP if you already have Text Editor installed.

• STEP 4

Go to File Station / Docker / homeassistant folder and open the file configuration.yaml Follow the instructions in the image below.

• STEP 5

Add the lines below in the configuration.yaml file and remember to change the Gateway IP with your own Gateway IP (see STEP 2). Save the file. Follow the instructions in the image below.

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.17.0.1

Note: If you use Home Assistant on host network instead bridge you should add your NAS Local IP on the trusted_proxies area. See the example below.
Note: If you type in your NAS Local IP and it’s not working, try to add 127.0.0.1 instead of your local NAS IP.

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - YOURNASLOCALIP
    - 127.0.0.1

• STEP 6

Restart the Home Assistant Container. Follow the instructions in the image below.

• STEP 7

Go back to STEP 1 or you will deal with karma 🙂

• STEP 8

Now you can access your Home Assistant over HTTPS once again if you have correctly set up the Reverse Proxy by following my Wildcard guide.

This post was updated on Thursday / October 6th, 2022 at 12:07 AM