Comment

Comment on Help getting started with self hosting Jellyfin via NAS?

ampersandrew@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

Sorry, but the SEO on “Q2” is pretty bad. What are you referring to? And what are the actual risks of a port being exposed to the outside world via an off-the-shelf router? Surely they can always hit my IP, and if this port is only exposed for Jellyfin, it would be just as vulnerable as any other port that calls out, right? I ask that knowing that it must be wrong, but I don’t understand how.

source

Sort:hotnew top

illusionist@lemmy.zip ⁨3⁩ ⁨weeks⁩ ago
There is always risk with exposing something to the Internet or untrusted people. You need to take steps to mitigate the risk.

Make sure you patch make sure you only expose as little as possible use https/tls have good, automated, tested backups to media that gets disconnected! having access logs enabled Isolate and separate from any private/internal stuff as much as possible. Separate hardware separate VLANs separate VMs

reddit.com/…/is_it_dangerous_to_open_http_ports_t…
source
- trewq@lemmy.world ⁨3⁩ ⁨weeks⁩ ago
  That’s why my reply to use vpn. Wireguard is silent, so it won’t respond without valid key.
  
  source
trewq@lemmy.world ⁨3⁩ ⁨weeks⁩ ago
Short for question #2

source
- ampersandrew@lemmy.world ⁨3⁩ ⁨weeks⁩ ago
  Oh, sorry, haha. There’s a lot of jargon thrown around in a sub like this, and I thought this was one I missed.
  
  source
  - trewq@lemmy.world ⁨3⁩ ⁨weeks⁩ ago
    No worries, sorry for using shortand. I was on phone and I always misclick with soft keyboard, so I tend to use shorthand there.
    
    source