Setup on Synology NAS with remote access

@feron
in NAS configuration:

  1. In External Access, DDNS sector I registered: “myname.synology.me”, I selected Auto for External Address and then generate a certificate for it
  2. By Reverse Proxy I create
    a) “dsm.myname.synology.me” for DSM interface and Destination Port 5001 to 443, WebSocket as your guide, and then its certificate
    b) “home.myname.synology.me” for HA and Destination Port 8123 to 443, WebSocket as your guide, and then its certificate

In your router (my case FritzBox)

  1. do “Port forwarding” of your NAS-device and release the port 443

hope that helps

Hello Protoncek, Hello Thanh-Binh

Thank you for your answer. Now, I’m able to connect from remote with ha.xxx.synology.me. But now I’m getting a certificate error on my IPhone (external URL in Home Assistant App). Do you know how to fix that certificate problem?

Screenshot 2022-11-05 171909

@feron Sorry, I do not know. At that time, I read the userguide of Protoncek, and repeat it again.
Where do you install HA? in Docker or VM?

I installed Home Assistant on docker. Can you send me print-screens of your certificate site on synology and also from reverse proxy, so I can check my settings.

Did you create cerfiticate and assign it? Go to security, certificates and create a new certificate for your new subdomain, then click “settings” and assign this new certificate to your new page.
On phone you’ll might need to clear cache.

Thx for the guide. I got pretty far.

I have HA running on docker on my NAS (no VM support).

I got dsm.username.synology.me working with certificate

I followed the the same process for ha.username.synology.me however I get synology Landing page saying “page not found”.

I my HA docker IP is the same as my Synology, so the only difference when creating the reverse proxy is the port number. Do I have to change something to get it working? I also add the lines to configuration yaml.

Any advise would be great.

Maker change in docker/homeassistant configuration.yaml
add lines :

http:
use_x_forwarded_for: true
trusted_proxies:
- 127.0.0.1

I got caught out by not setting the reverse proxy protocol to http, if left at https you will get the same issue.