I created a short tutorial on using sub domains to access services hosted within my home network, thought I would share it here in case anyone finds it useful

This is the first time I've made a technical tutorial so apologise if there are mistakes/its confusing, feedback will be appreciated

all 49 comments

sorted by: hot top controversial new old
[–] 24 points 10 months ago (1 child)

Thanks for sharing!

I can recommend nginx-proxy-manager for people who do not want to fiddle with proxy config files.

  • source
  • hideshow 1 child comment
  • [–] 15 points 10 months ago (1 child)

    I personally use caddy as a reverse proxy

  • source
  • hideshow 1 child comment
  • [–] 10 points 10 months ago (1 child)

    You seem to have descibed your port forwards backwards It is the router forwarding the ports to the gateway pi (and potentially other devices), not gateway pi and other devices forwarding to the router. The forwards to servers are incoming from the internet.

    (Theoretically you could have your pi physically between the router and the internet (modem) acting as a sort of pre-router, but this would be unusual. Perhaps you could describe your physical setup more clearly. What is physically/wirelessly connected to what, to the internet.)

  • source
  • hideshow 1 child comment
  • [–] 3 points 10 months ago

    He does refer to the pi as a gateway, so you would be right about it coming before the router. In that case, the pi would be the device handling NAT and forwarding ports.

    So I think he's describing it accurately... it's just not a common setup to see these days.

  • source
  • parent
  • [–] 7 points 10 months ago (1 child)

    I did similar with caddy. I own a domain and my server runs pihole and it is configured as DNS server. So what I did was setup caddy to create local subdomains that are only reachable through my network. For example: subdomain.mydomain.com , that works only from home. It works with ssl as well

  • source
  • hideshow 1 child comment
  • [–] 6 points 10 months ago (2 children)

    @JackDavies nice, thanks for sharing. This looks a lot like the setup I used to have until I decided I was not comfortable (nor experienced enough) having my Pi (and my whole network) exposed to the internet.A few tips/recommendations I can share from my experience:Namecheap includes free dynamic DNS hosting with all their domains, which means you can have your own domain and this reduces the chances of your sites being blocked due to others abusing free dynamic DNS services. You can get a cheap $2/year domain instead.For an even smoother TLS certificate experience, you can use Caddy, which is as easy to configure and run as Nginx, with the added benefit of automatic TLS certificate management.I know many people are not happy with Cloudflare, but their Zero Trust tunnel service is amazingly easy to use and covers 99% of use cases (I made up that number). Instead of exposing your entire network, you just make an outbound connection by running the cloudflared daemon inside your network and then create the subdomains by creating “apps.” No port exposing or routing.As for the post itself, I would only recommend replacing your mydomain.com examples with one of the official domains used for technical documentation: example.com, example.org, or example.net. These cannot be registered by anyone, which means you are not creating links to potentially dangerous sites.Good luck with your #selfhosting adventures!

  • source
  • hideshow 2 child comments
  • [–] [S] 2 points 10 months ago

    Thanks for the tips, I'll have a look at namecheap, I had the domain I've used rattling around for a while and wanted to do something with it

    I'll probably do something similar to that setup in the future, this was a quick fix

    I have updated the post to use example.com

  • source
  • parent
  • [–] 2 points 10 months ago

    I know many people are not happy with Cloudflare, but their Zero Trust tunnel service is amazingly easy to use and covers 99% of use cases (I made up that number)

    +1 for the evil Cloudflare Tunnels/Zero Trust. I don't go in blindly tho. Good points have been made on both sides of the conversation. Their free tier is very generous and I didn't need everything it offered, but it's there should the need arise.

    Namecheap.......You can get a cheap $2/year domain instead.

    That's what I did. It was less than $5 USD

  • source
  • parent
  • [–] 20 points 10 months ago (18 children)

    I am once again recommending that you not expose any services to the internet except a VPN

  • source
  • hideshow 18 child comments
  • [–] 16 points 10 months ago (10 children)

    Good as a general recommendation.

    I also feel like the risk levels are very different. If it's something that performs a function but doesn't save/serve any custom data (e.g. bentopdf), that's a lot easier to decide to do than something complicate like Jellyfin.

    I do have public addresses for Matrix, overleaf, AppFlowy, immich because they would be much less useful otherwise. Haven't had any problems yet, but wouldn't necessarily recommend it to others.

    I'd never host any stuff with "Linux ISOs" on a public adress, that seems like it'd be looking for trouble.

  • source
  • parent
  • hideshow 10 child comments
  • [–] -5 points 10 months ago (9 children)

    Doesn't matter. Any exposure risks compromise. From there, an attacker could pivot to read your data, mine cryptocurrency on your device(s), serve objectionable material, or other unsavory activities.

    Even if you have authentication enabled, not all APIs require authentication. Jellyfin in particular is not designed to be internet-facing. And even if it does require authentication, authentication bypass attacks are a thing.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 1 point 10 months ago (6 children)
  • [–] 1 point 10 months ago (4 children)

    Designed meaning in that case intended to be exposed.
    More of an internal thing.
    VPNs on the other hand are designed to be exposed. Same with some ssh servers or reverse proxies like traefik, nginx etc.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 10 months ago (3 children)

    So you mean the JellyFin ports should not be directlly exposed, but self hosting and exposing nginx to forward the traffic locally to jellyfin is fine?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 10 months ago (2 children)

    Better rather than worse, yes.

    Just need to be aware if what you expose and how and where.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 10 months ago (6 children)

    I'm not sure that's gonna work with my Jellyfin 🤔🫤

  • source
  • parent
  • hideshow 6 child comments
  • [–] 7 points 10 months ago* (5 children)

    I mean it WOULD work you would just need a von on every device you wanted to use.

    The REAL answer is never host them DIRECTLY, always use a reverse proxy like nginx. Many projects (i believe jellyfin is one of them) explicitly recommend this for better security. Which it looks like you did so congrats

    For extra bonus points you can setup nginx to run as a non privileged user and use iptables to forward the lower ports (80/443). A pain but closes out a large chunk of nginx as a risk.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 4 points 10 months ago (1 child)
  • [–] 1 point 10 months ago

    Eh, i just use pubkey only Auth config (so password entirely disabled as an option) and put ssh on a non standard port to reduce script kid noise. (and no 2222 is not non-standard it may as well be the default)

    Fail2ban triggers false too often for my taste in a high traffic environment.

  • source
  • parent
  • [–] 3 points 10 months ago (2 children)

    Did you learn that about my jellyfin by looking at my post history or connecting to my server? 😀

    It'd struggle a bit on some setups, like when I'm using the Jellyfin app on my GFs smart TV.. Or explaining to a friend in Europe how to setup a VPN without breaking anything else on his network... It is a risk for sure.

    I'm too tired right now to parse what you mean about the port forwarding. I guess the idea is to reduce the impact if Jellyfin were breached or exploited. If you're up for it, can you explain more about why that relates to port forwarding?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 10 months ago (3 children)

    Not positive, but I think you left in a reference to real info (twilightparadox.com) instead of "example-fying" it (mydomain.com), in the paragraph just before section 4:

    For example say I have home-assistant running on a Pi with the local address 192.168.0.11, I could create a subdomain named ha that has the value mysub.twilightparadox.com then create the following nginx config

    server{
    	listen 80;
    	server_name ha.mydomain.com;
    	resolver 192.168.0.1;
    	location / {
    		proxy_pass http://192.168.0.11/;
    	}
    }
    

    When nginx sees a request for ha.mydomain.com it passes it to the address 192.168.0.11 port 80.

  • source
  • hideshow 3 child comments
  • [–] [S] 1 point 10 months ago (2 children)

    I'm not sure which reference you are referring to, twilightparadox.com is a domain on the dynamic DNS service, mysub is also an example

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 10 months ago* (10 children)

    Very cool, great work!

    Worth noting about this approach is that the global list of subdomains is publicly searchable. So, you'll see vulnerability and AI scans on those endpoints.

    If that's a concern for you, using path-based routing (e.g. Apache VirtualHost) allows you to use difficult to guess paths to your cloud.

  • source
  • hideshow 10 child comments
  • [–] 1 point 10 months ago (9 children)

    Worth noting about this approach is that the global list of subdomains is publicly searchable.

    Can you expand on this? What is it that you call the "global list of subdomains"?

  • source
  • parent
  • hideshow 9 child comments
  • [–] 5 points 10 months ago (2 children)

    Certificate transparency, unless you use wildcard certs

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 10 months ago (5 children)

    It trivial to get a list of all registered domains and subdomains and the IP addresses they map to. There are any number of paid services to make it easy (e.g. https://subdomainfinder.c99.nl/) but I'm pretty sure there's also a way to do it yourself.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 5 points 10 months ago* (last edited 10 months ago) (3 children)

    Except it isn't. Saying it is trivial is just gross generalization. It's trivial to configure bind to have internal zones that aren't resolvable publically. It all depends on configuration, such as reverse ns entries, zone accessibility, etc.

    You can have (sub)domains that are listed in the certificate lists and yet aren't resolvable externally as well.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 10 months ago* (last edited 10 months ago) (1 child)

    Actually, wait. Something you a said might actually be just what I'm looking for: you mean that I can have DNS entry for mydomain.com and no additional CNAMEs, and have a cert for nextcloud.mydomain.com (or wildcard maybe?) and somehow still be able to use name based virtual servers?

    Hmmm. I thought I was going to be limited to path-based.

    Explain more?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 10 months ago* (last edited 10 months ago)

    Absolutely. Simply use ACME with the DNS validation method. Using bind you'll want to create keys and allow TXT access for those keys to the validation domains. Fear not, this isn't exclusive to bind, ACME tools supports dozens of other backends. That's all you need the actual domain doesn't need to be resolvable with an A/CNAME record. Internally you can run an entirely different DNS server to resolve your hosts, use hosts files, or use bind zones.

  • source
  • parent
  • [–] 0 points 10 months ago*

    Okay. Yup, that's probably true. I'm not that deep into network stuff. But, if you're just doing the basic, 'ha.mydomain.com => 121.41.38.9' that works out of the box with name based virtual hosts and reverse proxy, then yeah, you'll get traffic on that within 24 hours.

    I reckon if a person understands what you're talking about though, they're already doing better than most.

  • source
  • parent
  • [–] 2 points 10 months ago* (last edited 10 months ago)

    Oh excellent, thanks for sharing.

  • source
  • [–] 1 point 10 months ago (1 child)

    Oh I thought it was sub domains for localhost. I actually wonder now if that's possible.

  • source
  • hideshow 1 child comment
  • [–] 1 point 10 months ago