The more I am selfhosting the more ports I do open to my reverse proxy.
I also have a VPN (wireguard) but there are also 3 family members that want to access some services.
Open ports are much easier to handle for them.
How many users do you have and how many ports are open?
My case: 4 users (family)/ 8 reversed proxy ports
How many users and open ports have you?
You must log in or register to comment.
You’re comparing apples and oranges, reverse proxy and VPN serve two different purposes.
Though in this context they’re both being used to provide safe access to local hardware from the internet.
They probably want the pros vs cons of this specific situation
Both. Some things are only resolvable internally or over wireguard. Some things are publicly accessible via a reverse proxy.
Overseerr, bitwarden, plex all have ports open or through the reverse proxy. Same with email and a few other services. All the *arrs are accessible only on my network or over VPN.
this is the way.
also fail2ban to ensure that nobody bruteforce it’s way in.
Curious why you keep the arrs internal only, when there are things like Authelia that could secure access to them?
Because no one needs access externally. Overseerr is public facing and passes the requests to the arrs.
It’s not about secure access, it’s that no one outside my house, me included, really needs access to them at all.
VPN because I don’t know enough about all the random arrr services to expose them trustworthily.
Reverse proxy and allowing connection only to IPs from my country.
Out of curiosity, how do you accomplish that?
I’m using an nginx reverse proxy with maxminddb for geo filtering. I have it limited to my state instead of country. If I could reliably go more specific I would. I really only rely on external access to the reverse proxy for family. I could use a vpn myself but I’m not bothering with the inevitable and endless questions from family.
I don’t know if it’s realistic or not but I would love to use a client certificate to authenticate with the reverse proxy but I’m not sure of the compatibility with mobile devices or smart TVs. If it would work even a self signed cert that’s valid for years would be a nice layer.
Cloudflare DNS basically, but it can be implemented at nginx level using geoip2 modules (I do both, because some of my services don’t play well with Cloudflare proxied DNS). The cumbersome part is keeping geoip database up to date but I’m sure there are plenty of tutorials online.
I know cloudflare has a free tier and allows you to put rules like this in place. AFAIK you’d have to use them as DNS at least in order to use this feature. I use Cloudflare tunnels and access to facilitate remote access to my home-server, and I know I have this same rule in place.
Tailscale with reverse proxy, nothing publicly exposed
Do you even need a reverse proxy if you’re using Tailscale? What advantage does it give you over setting up your DHCP correctly such that you can access your services by hostname?
Because I have my own custom domain internally and don’t use tailscale while on I’m on my network physically. But I get the best of both worlds, however I do have Tailscale setup with DNsMasq to set to my domain name anyway instead of using the Tailscale domain
I’ve got a reverse proxy for stuff I want to be able to hit from the outside. It’s behind an SSO portal with 2fa (hardware token). Then for everything else I VPN in.
What are you using for SSO?
Not op, but I’d recommend looking in to keycloak.
I’m not OP but Keycloak is pretty usable for SSO. I’ve configured about 8 different web apps to be integrated with it via OAuth2.
Wireguard, as only a handful of people need access to the services, I manage it manually - and not with Tailscale or something similar.
With that my server looks nothing like a server from the outside, as I’m exposing nothing - Wireguard doesn’t even show up in a port scan
I like this approach, but I’m currently sitting in a foreign hotel who’s wifi seems to block WG. Annoying. Keep a TLS-protected reverse proxy for things you might need through obscure networks.
Probably the usual. 80/443, wireguard, a couple game servers.
For those of you who staunchly put your open ports on a VPS and wireguard tunnel it back to your home server, are you firewalling that wg connection to only allow specific traffic?
I used to, but less so now, I get that weakens the separation.
Mostly the vps is hardened to f and that’s my defense but I agree it’s a bad one.
A reverse proxy isn’t a substitute for a VPN for access outside your network. And it isn’t any less secure; you only need to open 1 port however all of your services will be accessible via that single port which is arguably less secure.
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 SSL Secure Sockets Layer, for transparent encryption SSO Single Sign-On TLS Transport Layer Security, supersedes SSL UDP User Datagram Protocol, for real-time communications VPN Virtual Private Network VPS Virtual Private Server (opposed to shared hosting) nginx Popular HTTP server
[Thread #60 for this sub, first seen 18th Aug 2023, 07:55] [FAQ] [Full list] [Contact] [Source code]
deleted by creator
Never open ports to the internet unless you want everybody to see it. Always use VPN to access your selfhosted stuff. If you’ve got a lot of VPN connections to set up, try generating a QR code for the connection. Makes it a bit faster to setup the client.
Caddy Reverse Proxy with Basic Auth for services which are critical like my 3d printer. Without auth for other services like my website or jellyfin and such. I use docker for everything so that’s another layer of safety for me.
I have port 443 open and use subdomains for most stuff. Some other ports for non-HTTP services but I don’t have any right now.
I use a self-hosted vpn, because I don’t want to expose anything to the internet. The ones I do want to, I haven’t set up yet since it would require reinstalling my pi. But I do have a reverse proxy set up on a vps that I will use once I get around to doing it.
Depending on the services you provide, the usual standard ports. So if you run http/https services, port 80 and 443 respectively.
You seem to answer your own question.
