Perfect that did it (No changes to HA Hassio just works after this change)
Synology NAS are the perfect companion to running Home Assistant. But by default, the DSM Reverse Proxy does not configure its NGINX settings to allow WebSocket, and some extra configuration will be required to get the Home Assistant frontend working with the DSM.
To allow WebSocket by default for all service exposed by NGINX, you can enable it in the template file located in /usr/syno/share/nginx/Portal.mustache. Please be really careful in editing this file since you may break access to the DSM UI. Please backup this file before any edition.
Open /usr/syno/share/nginx/Portal.mustache and add the followings in the Location section:
ONE THING: I would still like to know if I could make some kind of redirect for all HTTP to HTTPS on the HA
So any access to the a HTTP://IP:PORT is redirected to the new default working HTTPS://DOMAIN.COM
That part is still not working (Only port open is 8123)
Only made the change to the Synology, and didnt install nginx on the Home Assistant
and I could see that if I tried to access the https domain on the local wlan it would hang on the login screen
So I installed NGINX on Hassio and wanted to do the proposed changes listed here:
Couldnt find the files they talk about here:
Copy the Home Assistant specific Reverse Proxy settings from the existing /etc/nginx/app.d/server.ReverseProxy.conf file to /usr/local/etc/nginx/conf.d/http.HomeAssistant.conf.
Include these lines in the location declaration:
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “upgrade”;
But I am not sure on how to do this, in the Hass.io config for “NGINX Home Assistant SSL proxy” I have changed this by adding the last lines:
The changes need to be made wherever you want to use the proxy.
Think about this.
You have a reverse proxy, that is proxying all requests back to a backend endpoint. You need all the settings to be correct on your entry point which is your proxy, in order for it to pass through the data.
If you try to stick another reverse proxy behind a reverse proxy, you still are not passing the data through to the client correctly.
Yes, any changes you make need to be made on the instance that is actually performing the reverse proxy.
After, the new, update 1 I had connection problems with https-connections (even within my LAN). Removing the manually added proxy_read_timeout line (see two posts above) did solve this problem. HA seems running perfectly now.