Suppose you have already used my Synology Wildcard guide to get Home Assistant Supervisor to work over HTTPS. If you are getting a 400: Bad Request error when you try to access your Home Assistant Supervisor via HTTPS, then you’re not alone. In today’s article I will teach you how to fix the Home Assistant Supervisor error and access your Home Assistant Supervisor over a secure HTTPS connection.

• STEP 1

Please Support My work by Making a Donation.

• STEP 2

Install Text Editor via Synology “Package Center”. (Mandatory STEP.) If you already have Text Editor installed on your Synology NAS, skip this STEP.

• STEP 3

Go to File Station / Docker / homeassistant folder. Double click on the homeassistant folder to open it. Follow the instructions in the image below.

• STEP 4

Once you open the homeassistant folder at STEP 3, double click on the homeassistant folder. Follow the instructions in the image below.

• STEP 5

Open the configuration.yaml file. Follow the instructions in the image below.

• STEP 6

Add the lines below in the configuration.yaml file. Click the X to save the file. Follow the instructions in the image below.

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 127.0.0.1

• STEP 7

Open the Docker Package. On the left sidebar click Container. Stop the homeassistant container. Follow the instructions in the image below.

• STEP 8

Open the Docker Package. On the left sidebar click Container. Start the homeassistant container. Follow the instructions in the image below.

• STEP 9

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

• STEP 10

Now you can access your Home Assistant Supervisor over HTTPS once again if you have correctly set up the Reverse Proxy by following my Wildcard guide and remember that Home Assistant need WebSocket activation in order to work properly via HTTPS.

This post was updated on Friday / January 27th, 2023 at 12:23 AM