Comment on OMV remote access
Xanza@lemm.ee 1 month ago
But I’m a bit lost which approach and tools to use without exposing and making my NAS vulnerable on the internet.
You’re looking for a reverse proxy;
*.domian.dev { encode zstd gzip @jelly host jelly.domian.dev handle @jelly { reverse_proxy {selfhost_ip}:{port} } @ping host ping.domian.dev handle @ping { respond "pong!" } }
Running caddy like this directly connects your jelly.domain.dev
domain to your selfhost ip on a specific port. From within your selfhost you ensure that you’re only allowing in the IP of the VPS, so no one can else can directly connect.
Works great.
TentinQuarantino@feddit.org 1 month ago
Thank you for your tip! Reverse proxy was one of the techniques I was referencing in my post. But somehow I didn’t get how this thing functions. It’s easier than some might think actually. But on the weekend I have to sit down and nail it down to a solution