Running reverse proxy on Synology, "unable to connect" from HASS on Pi

[lynchpin (Lynton)]

Hi all,
I have set up reverse proxies using the built in RP manager in Synology DSM 7. Everything is working as expected on that machine, and I can access my Docker containers using the hostnames I’ve defined. I have a Pi running HASS on the same network, and after a lot of tinkering I’m close (I think) to getting it to work. I was getting a 400 error initially, but then I added a trusted proxies entry to my HASS config. Now it’s hitting the HASS instance on the Pi, but I get the HASS splash screen and an “unable to connect” error. Here’s the RP setup on my Synology:

YAML:

homeassistant:
  external_url: https://hass.mydomain.synology.me
  internal_url: http://192.168.1.80:8123

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 192.168.1.50

(My Synology is at the 1.50 address, the Hass Pi is at 1.80)

Certificates are managed on the Synology, and they work fine with Docker containers. Can anyone spot what I’m doing wrong?

Any help would be greatly appreciated!

[mirekmal (Mirek Malinowski)]

Have you added websocket to your configuration?

Choose Custome Header, click on Create and then Websocket. Options like on screenshot above will be added and then you should be able to connect.

[lynchpin (Lynton)]

Mate, I could kiss you. Thank you so much! I have no idea what that is (I’ll do some Googling) but it made it work immediately.

Absolute legend - thanks so much.

[VictorHugenay]

Thank you that was the solution