This guide has been migrated from our website and might be outdated. Feel free to edit this guide to update it, and to remove this message after that.
Synology NAS is 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.
Setup headers
Starting with DSM 6.2.1+, you can create “custom headers” in the Application Portal:
- Go to Application Portal and edit your entry
- Click on “custom headers” tab and click the dropdown on the “Create” button
- Select “Websocket”. This will automatically add the required headers for WebSocket to this reverse proxy.
- Click “OK”. Home Assistant should work now with the reverse proxy.
It’s not necessary anymore to change the template anymore since Version DSM 6.2.1. Changing the Portal.mustache is not recommended! You should use the following part only if you’re using a Version before DSM 6.2.1. on your Synology.
Template change
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:
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_read_timeout 86400;
Then restart the NGINX daemon:
sudo synoservicecfg --restart nginx
This will restart the running HTTP service, not only reverse proxy, as a single instance of NGINX runs everything.
You can find more information here.
HTTP Configuration
- Copy the Home Assistant specific Reverse Proxy settings from the existing
/etc/nginx/app.d/server.ReverseProxy.conffile 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";
