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

you are viewing a single comment's thread
view the rest of the comments
[–] 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