Hi all, planning on purchasing a NAS, Synology appears the way to go. Can anyone recommend which model and hard drives play nice with HASS? I use a Mac, and am looking at 2Tb storage.
Cheers
I have a DS916+ running ironwolf HDD. Use it for videostation and HASS. Works great.
I have a small Synology DS216 and 2 Microservers a Gen7 and Gen8 running Xpenology they worked out much cheaper with more power and all the benefits of Synology DSM.
Both micro servers have 4 4TB Western Digital Reds.
I have DS916+ as well and it works really great. I just went from having Hass on an RPi 2 to installing it in a Docker container on the Synology. I’m amazed how much faster it’s running on the Synology compared to the RPi. It’s also very convenient to have everything running in Docker containers.
I recommend readynas over Synology. I’ve been burned a few too many times by synology hardware and support.
OK my NAS (DS216+II) is en route, and I intend on running HASS in Docker on it. Do people doing this also run their MQTT broker on the NAS, in a Docker?
Do people port forward to their HASS instance on NAS for outside access? Any other options which don’t require an open port?
I have encountered the issue https://github.com/SynoCommunity/spksrc/issues/2581 Have you got the package working? Alternative would be docker?
I’ve got a DS1512+ with 5 3TB Western Digital Red hard drives in it. It’s been going like a champ for 4 years now.
I have it running through port 443 so that I can access it from corporate systems that block all ports except 80 and 443. Use the reverse proxy to forward it to https DSM port.
hi @gbboy,
I have a synology DS916+, using HA in a docker. Last week i configured the proxy reverse using port 443, because also in corporate block all ports except few ones.
When i try to access to HA by proxy reverse using https the main website is showed to me and asking password, once i put password, then HA think to much, and after few seconds, tell me that i can’t access (try again) and password is correct.
Did you have this problem? how did you solved?
I have other collegue, that also configured the proxy reverse, and he has the same problem as me.
One more thing, if i try to access via VPN https://IP:8123, then works well.
thanks
I didn’t experience any issues like that. I actually haven’t even specified the DSM reverse proxy to forward to ha. The only thing I’ve done is making sure my base_url was the sub domain I wanted ha to be accessed from e.g. https://ha.mydomain.com . With port 443 open it automatically exposes my ha setup
Hi,
I have exacly the same as your configuration:
https://ha.mydomain.com with port 443 forwarded in my router.
In the proxy reverse i have that this domain: https://ha.mydomain.com with this port, must go to http://IP:8123.
Do you have the same? or in your case the redirection of you subdomain goes to https?
thanks
My router has port 443 forwarding to port 443 on the 916+. In the HA configuration I have set the base url as https://ha.mydomain.com
I have not set the DSM reverse proxy with any forwarding rules for HA. The name server of my domain points to my routers IP and automatically gets routed to HA when I use that url.
For other things like DSM plex or the DSM interface itself I do have the reverse proxy setup as you described. It is all https url redirects from 443 to https:// localhost and the specific port.