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
[–] 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