202

Assuming the user will not be connecting over vpn, but is both remote and non-technical, how would you expose Jellyfin to them securely?

you are viewing a single comment's thread
view the rest of the comments
[-] NeryK@sh.itjust.works 12 points 3 weeks ago

For a remote and non-technical user I would say IP whitelisting offers a decent tradeoff.

On your end you expose your jellyfin port to internet, but restrict at the router level to your user's client IP address as soon as you have it. Obviously in practice this works best if the address does not change often.

[-] Bazoogle@lemmy.world 4 points 3 weeks ago

Also not as ideal if their ISP uses CGNAT. Still waaay better than fully open, but you would be giving access to many households

[-] NeryK@sh.itjust.works 1 points 3 weeks ago* (last edited 3 weeks ago)

Yep, that's why I call that a tradeoff. Far from perfect and yet so much better than nothing.

Pros:

  • Likely cuts 99.99% of attacks.
  • Nothing to do on client's end.

Cons:

  • Whitelisting must be updated everytime the client address changes.
  • Not 100% bulletproof as operators (notably for mobile networks) can NAT multiple connections behind a single publicly addressable IPv4 address.
  • Also IP addresses can be spoofed but I doubt that would be a major concern here.
[-] MIDItheKID@lemmy.world 1 points 3 weeks ago

Is there a way to this with like a MAC address instead of an IP? Allowing specific devices (my parents have a Firestick that they travel with) would be pretty ideal.

[-] NeryK@sh.itjust.works 3 points 3 weeks ago

No, not for remote access over the internet.

this post was submitted on 23 May 2026
202 points (97.2% liked)

Selfhosted

59955 readers
307 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS