I run a load of containers on a NAS, and reverse proxy them through synology’s inbuilt reverse proxy settings.
Essentially, I’d like to harden my security, and not really sure how best to do it.
Seeing people recommend nginx proxy manager, I’ve tried to set this up but never managed to get the certificates to work from letsencrypt (“internal server error” when trying to get one). When I finally got it working a while ago (I think I imported a cert), any proxy I tried to setup just sent me to the Synology login page.
I’ve tried to setup the VPN that comes with Synology (DSM 7+), but I must have set it up using the local IP address. It only works when I’m on my LAN, and not from an external network. Which is kind of the point, lol. I would like to use VPN to access the home network when out and about.
I’ve set random, long, unique passwords for everything I want to access, but I am guessing this is not the most secure, after seeing so many people use and recommend vpns.
I have tailscale, which is great for ssh-ing onto my Nas from the outside world. But to access my services, is a VPN the best way to do it? And can it be done entirely myself, or does it require paying for a service?
I’ve looked at authentic - pretty confusing at the outset, and Isee few evenings of reading guides ahead of me before I get that working. Is that worth setting up?
Does anyone have any advice/guides/resources that might help?
You must log in or register to comment.
Seeing people recommend nginx proxy manager, I’ve tried to set this up but never managed to get the certificates to work from letsencrypt (“internal server error” when trying to get one). When I finally got it working a while ago (I think I imported a cert), any proxy I tried to setup just sent me to the Synology login page.
I think WebStation is causing this. I just investigated my Synology NAS and discovered that the default web portal is redirecting ports 80 and 443 to the synology login portal (which lives in ports 5000 and 5001 depending on whether you use SSL or not.)
I have tailscale, which is great for ssh-ing onto my Nas from the outside world. But to access my services, is a VPN the best way to do it?
The main point about Tailscale that I see people on here often get wrong is that they compare it to a “classic” hub-and-spoke VPN, when in fact it is an end-to-end zero trust encrypted mesh network. End-to-end does not mean machine-to-machine, it means user to service. So in your case, you should place one tailscale node in each pod (collection of containers that make up one service) as a sidekick. That way, a user need to authenticate in order to even open a network connection for a specific service, which is a very secure solution.
You don’t need to create a separate Tailscale node for each service. One Tailscale container, with its docker network interfaced with any container that needs it. Not sure what you’d gain by having multiple nodes in a scenario like this with a single user.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters DNS Domain Name Service/System HTTP Hypertext Transfer Protocol, the Web IP Internet Protocol NAS Network-Attached Storage SSH Secure Shell for remote terminal access VPN Virtual Private Network nginx Popular HTTP server
6 acronyms in this thread; the most compressed thread commented on today has 12 acronyms.
[Thread #361 for this sub, first seen 17th Dec 2023, 21:45] [FAQ] [Full list] [Contact] [Source code]
I don’t like Tailscale. Use a reverse proxy (nginx proxy manager makes this simple) and secure your services with fail2ban and/or crowdsec. This way you do not have to rely on Tailscale relay or their clients to connect to your services from anywhere.
Tailscale is (like) a VPN, but traffic will go through their servers. If you setup your own VPN server then traffic will remain between your client and your own server.
Did you setup port forwarding and routing tables when you installed your VPN server?.
The Synology VPN package is lacking behind a lot, so you could be missing some security updates.
If you use a VPN to hide your services, you reduce your attack/risk. Since there is only one package/software suite which could’ve vulnerabilties. And VPN’s are focussed on security. If you expose all your hosted stuff, all those programs need to be secure to prevent abuse. And not everybody is as skilled to build it securily.
I would recommend, for you, to use something like tailscale. Since you seem like someone at the beginning of their safety journey. With setting up a VPN server, you need to know a little bit what your doing to make it secure and work. And you could invest time to learn it all, or you could use something that does it for you. Another, not so wise, advise could be to use a docker container to host the VPN. Most containers have all settings correctly setup and have guides to make it secure. But that means you don’t know what you installed and that could be a bad thing as well. Furthermore, docker adds to the complexity of making it work.
Tailscale is (like) a VPN, but traffic will go through their servers.
That’s wrong. In a peer to peer VPN the traffic should not pass Tailscale infrastructure.
See their docs: https://tailscale.com/kb/1094/is-all-traffic-routed-through-tailscale
I definitely didn’t set up any port forwarding or routing tables when setting up the inbuilt VPN.
Tailscale is great, and very handy to edit my compose files from, for example, work. But I didn’t think I could use it to access my services?
I’ve become pretty familiar with docker over the years, so I’m tempted to spin up a container just to see how it works.
I currently expose around 20 services through the reverse proxy, but only those ones that I can set a user/password for.
I don’t mind investing the time to learn more about all this. Networking stuff has always been akin to dark magic for me, it’s time to jump in…
Thanks!
