Post #3778078

2026-07-06 00:41 UTC

Device -> VPN Tunnel (ideally WireGuard) -> Home Router / Server. The only port that needs to be opened is your WireGuard server which typically is :51820. The issue with this is you have explain VPN’s and WireGuard to people which, in my experience turns people away as they see it as a hassle. Alternatively buy a domain, setup DDNS so that your home IP is associated with your domain, setup a reverse proxy and open port :443 on your router however, I would suggest a blacklist-first approach and only whitelist the few known IP’s you can trust.

Replies (2)

@FlexibleToast@lemmy.world 2026-07-06 01:13

Free vps in oracle cloud with Pangolin. Never have to worry about explaining VPNs.

Open ##3778077
@ridethisbike@lemmy.dbzer0.com 2026-07-06 04:05

I did the last one. Bought a domain for $5 per year from cloudflare and used a cloudflared tunnel to direct traffic to Caddy (reverse proxy). Set up everything as deny-by-default, requiring log in to access things like sonarr, and let things like Jellyfin and Immich bypass the login requirement. Took a bit to get it all figured out, but it worked. There is also a way to use the cloudflared tunnel for free that gives you a domain as well (sort of anyways). All of that is run via docker containers, minus the Documentation on all of this is fragmented and a challenge to figure out. Happy to help anyone who wants to message me about it. I took this a step further as I use a wireguard tunnel to make use of my router level ad blocking. So I added an entry for my domain to route back to caddy and serve it all locally. This is proving to be a challenge due to the way some browsers handle forced https, but I’m making due.

Open ##3780680