How can you enable remote access on HomeAssistant installed on a Synology DS218+ through Docker?

Configuration
1

I have a domain name that I want to use to be able to access my Home Assistant that is installed in my Synology DS218+ in Docker.

I don’t want to use DuckDNS because it is blocked at my work.

Please help, thanks!
(Total newb here btw and still learning more about terminologies)

2
  1. You need to know your Public IP Adress
  2. This IP Adress should be configured in a Domain (A-Record)
  3. I recommend to configure an Reverse Proxy, you can do it on your DiskStation (Control Panel -> Application Portal -> Reverse Proxy -> Create)
    proxy
    proxy522×634 39.5 KB
  4. Add the Reverse Proxy Rules
  5. Add the Custom Header for Websocket (Create Websocket)
  6. You need to open Port 443 on your Router for the DiskStation
  7. Thats it

Good to know:

  • Your Public IP is changing every 24 hrs I guess. This is why you need DuckDNS or another Dynamic DNS Provider.
  • On your DiskStation you can also assign an SSL Cert for the Reverse Proxy (Control Panel -> Security -> Certificates)
  • Before you want to access external, you should prove if the internal way is working.
3

That is exactly how i do it and i used dyndns as my ddns solution, follow that guide above and you will be sorted in no time :slight_smile:

4

ahoy fellas! thank you for this suggestion, can’t wait to come home and try this solution.
btw, my Synology DS218+ NAS is already external accessible though “mycustomname.synology.me” with Let’s Encrypt.
this process wouldn’t interfere why my external address for my NAS right?

then for opening the port in Google Wifi, is it for TCP, UDP or both?
and 443 → 8123 is how I should input it right?

thanks a bunch!

5

I’m doing all of the above, but with duckdns. I can access the ha locally but via the external address I’m getting SSL errors, the ha log is also showing http errors. Does my http config require a change? I have the base URL only in the config. I have an open /ticket with a full breakdown of my problems.

[Synology reverse proxy HTTP errors]

6

I just tried this,

  1. cloudflare: added A record pointing to my external IP
  2. Opened google wifi for NAS local IP TCP/UDP 443 - 443
  3. Added reverse proxy rules:
    Source: https, mycustomdomainname.com, 443 , checked enable HTTP/2
    Destination: https, NAS Local IP, 8123
    Clicked custom header tab, clicked create, Clicked Websocket

when I go to my mycustomdomainname.com on the browser, nothing loads.
Note: it addes a port 5000 at the end (mycustomdomainname.com:5000)

7

I was finally able to make it work.
I had to add another certificate from LetsEncrypt that is specifically for the domain I’m using.

8

Did anyone stumble with the Lets Encrypt certification - mine’s telling me to check my ip and reverse proxy?

I’ve followed the above:

  1. Create A record pointing to my public ip
  2. Setup port forward rule for 443 TCP/UDP to point to my NAS local IP port 443 on my router
  3. Setup reverse proxy (same as above screenshot)
  4. If I try going to my domainname, in a browser it hangs, then times out