i have two synology, 1520 and 1522. both with reverse proxy. the 1520 is working, however the 1522 wont work. how to get both to work as router can only forward to one nas?
I'd be really interested in a discussion over what is the best performance wise? DSM Reverse proxy (RP) / a busy DSM RP (lots of services / apps / containers running)/ running NGIX as a docker on DSM / NGIX docker on another box
So performance wise, pretty much any synology out there will easily saturate any internet connection, so the bottleneck will almost certainly be somewhere else
@@SpaceRexWill If you add a lot of reverse proxy entries (+25 or so from memory), Synology runs into all sorts of issues when updating packages and takes ages to enter/change reverse proxy entries. Reported the issue to Synology over a year ago and still not fixed.
@@blakrj Same issue here. I was happy to find this DSM functionality an year ago but I am disappointed now. In fact I am moving all reverse proxy entries to traefik which is also responsible for Let's Encrypt certificates issued via DNS-01 (something many people also asked Synology to implement for many months).
The only thing I hate with Synology is that they have locked the possilibility to use asterisk (*) in domain certificates. Yes you can do it by code in Linux, but not in UI.
LOL, I was hoping to see OpenSpeedTest behind reverse proxy in action :) The issue I'm having is that upload speed shows unrealistically high (something to do with compression apparently), compared to accessing it directly via IP & port. Same setup as you, docker plus DSM 7.2 reverse proxy.
Why use the DNS server on the NAS? I use a wildcard certificate (Let’s encrypt with Synology DDNs) and just setup the reverse proxy on the NAS as you did. Doesn’t using the NAS’ DNS require each computer or client to use that DNS server?
This is what I was looking for! Thank you so much! Now time to show us how to do wildcard certs with Let’s Encrypt. :-D
Simple explanation for simple thing. Nice!
What is the point of the 'd' sub-domain level? Is that just to signify the domain as being defined by your local DNS server?
Very good video, thanks !
I have two WANs, in order to get DNS load balance, what should need to be done ? Can you also do a video about that?
Thanks for the great video Will!
3:00 sometimes a simple graphic would help
Nice one WIll, thanks
i have two synology, 1520 and 1522. both with reverse proxy. the 1520 is working, however the 1522 wont work. how to get both to work as router can only forward to one nas?
I have Nginx Proxy Manager running in a docker container. I would need to use one or the other correct?
Which one do you recommend for best security, reverse proxy, Cloudflare tunnel or quick connect?
Can I use this to proxy out multiple servers that I have on a Vlan?
Will this work behind CGNAT ? Please help ...
Thank you for this
can you make a tutorial on how to setup handbrake on synology. thanks.
I'd be really interested in a discussion over what is the best performance wise? DSM Reverse proxy (RP) / a busy DSM RP (lots of services / apps / containers running)/ running NGIX as a docker on DSM / NGIX docker on another box
So performance wise, pretty much any synology out there will easily saturate any internet connection, so the bottleneck will almost certainly be somewhere else
@@SpaceRexWill If you add a lot of reverse proxy entries (+25 or so from memory), Synology runs into all sorts of issues when updating packages and takes ages to enter/change reverse proxy entries. Reported the issue to Synology over a year ago and still not fixed.
@@blakrj Same issue here. I was happy to find this DSM functionality an year ago but I am disappointed now. In fact I am moving all reverse proxy entries to traefik which is also responsible for Let's Encrypt certificates issued via DNS-01 (something many people also asked Synology to implement for many months).
The only thing I hate with Synology is that they have locked the possilibility to use asterisk (*) in domain certificates. Yes you can do it by code in Linux, but not in UI.
LOL, I was hoping to see OpenSpeedTest behind reverse proxy in action :) The issue I'm having is that upload speed shows unrealistically high (something to do with compression apparently), compared to accessing it directly via IP & port. Same setup as you, docker plus DSM 7.2 reverse proxy.
From OpenSpeedTest website:
Warning! If you run it behind a reverse proxy you should increase post body content length to 35 Megabytes or more.
Useful vid
Can I get an ssl cert even for internal use only proxies like you just showed?
You would have to buy a wildcard cert
@ so getting a let’s encrypt directly from dsm won’t work?
@@redstormsju777yes, I use the Synology let's encrypt as a wildcard for multiple domains pointing to my NAS via Cloudflare DNS
Why use the DNS server on the NAS? I use a wildcard certificate (Let’s encrypt with Synology DDNs) and just setup the reverse proxy on the NAS as you did. Doesn’t using the NAS’ DNS require each computer or client to use that DNS server?
I had to setup the DNS to proxy to another NAS, if you proxy to localhost is not necessary
Thanks!
never buy synology bad support