470
Jellyfin over the internet (startrek.website)
submitted 1 year ago by to c/selfhosted@lemmy.world
265 comments fedilink hide all child comments
 

What’s your go too (secure) method for casting over the internet with a Jellyfin server.

I’m wondering what to use and I’m pretty beginner at this

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 1 year ago (6 children)

And this is the start of the longest crypto nerd fight I've seen on Lemmy. Well done, people!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 3 points 1 year ago (5 children)

    Not so much a fight as an exercise in futility lol

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 1 year ago (4 children)

    Well, I might as well put a dog in the fight. I'm considering my final, actually secure deployment of nextcloud.

    This discussion has convinced me that a vpn is the only answer.
    And almost everyone says wireguard.

    K. Thats what I will build.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 1 year ago (3 children)

    It’s not the only answer, but it’s the one that will get you the most secure with the least amount of effort.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 1 year ago* (2 children)

    Ya. I understand VPN. I do enterprise IT stuff. The things I build assume a secure environment. VPN is step one.
    Nailing down a web server on the internet tho ... there's so many ways to attack. There's so many things to secure. And its a bit complex to manage all that.
    The nextcloud site covers hardening the server, but doesn't even mention vpn.
    I've been watching threads like this. I'm pretty convinced vpn is the answer.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    Yeah Nextcloud won’t mention VPN for hardening because the assumption is you want it publicly accessible.

    I have a number of things publicly accessible and there are a number of things I do to secure them. crowdsec monitoring and blocking, a reverse proxy with OIDC for authentication, a WAF in front of it all. But those are only for the things I have exposed because I want other people to use them. If it’s something just for me, I don’t bother with all that and just access it via VPN.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 year ago

    Ok. Yes, my use case is a private document and media store. I'm ungoogling.
    VPN seems like a good place to start. But I'd like a simple answer, and I expect there are none to be had. As you've illustrated here, I'll find a reason to punch holes in the firewall. And then I'm going to need to secure a web server. Life happens. I'll keep it simple for now while I sort things. Thanks for your perspective.

  • permalink
  • fedilink
  • source
  • parent