Connect to DSM via port 443?

[jono]

I can connect to a DiskStation through one of my domains with an SSL certificate (https://mydomain.com:5001).

I have to have port 443 open in order to get/renew the certificate from Let's Encrypt and wondered if there's any reason why I shouldn't also use that port to connect to DSM on that DiskStation? (MyDomain | Domain Names, Web Hosting, and Free Domain Services)

 

[Rusty]

Have you tried to configure it via Revers proxy setting (Control Panel > Application portal > revers) to push 443 request to 5001 port?

 

[jono]

No, I haven't tried that yet (although I have run Traefik (reverse proxy) on an Intel NUC and used that to point a domain to my Synology in the past).

Just wondering if there were any reasons (technical or security) why we shouldn't use that port (and why Synology don't use it by default)

 

[Rusty]

Be default 443 and 80 are used by DSM (Web Station). Give it a go via revers proxy

 

[jono]

OK, thanks. Will do (I don't use WebStation anyway)

 

[Shadow]

I also use reverse proxy if I want to be able to access my DSM via port 443 (especially handy on restricted networks that only allow port 80 & 443 outgoing). Having my own domain is a great help tough.

https://dsm1.mydomain.nl

https://dsm2.mydomain.nl

etc..

 

[jono]

Another bonus when I used Traefik was that I didn't have to specify the port number on the end of the URL, as https URLs automatically use port 443

 

[Rusty]

yep, 443 is https default

 

[Gerard]

Does connecting to dsm on 443 have prevent you from connecting to a web server if one was set up? Can use 443 on one or the other?

 

[Rusty]

Well if you want to reach them all on 443 you will have to have your internal services on none 443 port and use a reverse proxy that will distribute your 443 requests to a specific service.

So for exp if DSM internally is on 5001 and you wanna reach it via 443 you will create a reverse proxy record that will point from source 443 to destination 5001. Samo for any webs. Internally you can host that web on let's say 1029 and again create a reverse record that will point 443 to 1029 for a specific hostname of that web. Problems solved.