This is the reason I didn't go with Plex when I was setting up my server.
this post was submitted on 16 Jun 2025
530 points (90.8% liked)
Selfhosted
48450 readers
360 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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Jellyfin is great, but in defense of Plex, they announced that remote streaming would require one of the two parties to have a Plex pass was coming back in March so I don't know if it's fair to say they are holding anything hostage.
I started down the Jellyfin path after they made that announcement. It's super easy to install, and in many ways the UI is nicer than Plex. But I ran into challenges getting my server safely accessible for users outside my LAN. And I haven't had the time to look into that further.
Would be great if there was a clean, easy way to set up the webserver portion so it's as easy to share content entirely as Plex. But I get they are a volunteer project with a lot on their plate.
load more comments
(27 replies)
load more comments
(20 replies)
What about switching to Jellyfin?
Already done. Thanks for the suggestion though. :)
load more comments
(1 replies)
As was stated on the first post you made about this, it's a dns or nat reflection issue.
Plex sees you accessing it through your external IP address, and not through your lan IP.
I had a similar problem, and had to roll back some nat changes I made, and now it's working fine again.
Meanwhile, free remote streaming works fine if you have a proper VPN setup. I just tested it, and was able to stream to my phone, through the Plex app, over my tailscale VPN, and I do not have Plex pass on the server or on my phone...
This sounds like a whole lot of convoluted bullshit to use Plex locally and "looking local" through VPN solutions when you could just roll a Jellyfin instance and do things a more straightforward way..
load more comments
(1 replies)
I did not make a "first" or "second" post about this. This is it.
Plex has pay walled FREE servers streaming to FREE clients only.
If you have a plex watch pass (for client) you're good and can stream from any server. If you have a plex pass (for server) any one can stream from your server. But you have to have one or the other.
For software I like made by people getting paid, I was happy to pay the one time fee. It's really good, secure, and downloads are fast now.
Ditto. There is a crowd on Lemmy who seem to get angry whenever people are happy to pay for software and I do not understand it. Surely we want developers to be paid for their hard work? Don't we want them to able to comfortably live?
Agreed. I've stated it before in other threads, and I'll say it again here, but if they asked me in 5 years to pay another $89 or whatever in continuing support for a badge on my server I'd happily do it. Plex is really good. Great UI, great apps, great external enrichments like trailers/subtitles/ratings/actor info, and Plexamp is 9.5/10 for music.
Their biggest fault is how they communicated about the change for remote users. I did have a few family members get the email and ask if they were going to have to start paying monthly now, but they've never been on a free server. They should have stated more clearly than if you were on a Plex Pass server that no change is required.
Best 70-ish euro I spent over a decade ago
And I just tested streaming from my free server to my free phone while said server is at my house, and my phone is with me at work.
Works fine over a VPN.
Yep, VPN will allow you to be on the same local network, and they're only pay walling remote play.
load more comments
(3 replies)
It's pretty rare that a company starts taking away free features and doesn't end up fucking payers in the end.
The biggest bar to Jellyfin is TV clients, the second biggest is security.
TV clients can be fixed with a one-time purchase of a $20 android TV stick. If viewing your familys ARR content isn't worth $20 you probably don't need to do it anyway.
Security for remote streaming is a harder thing to handle. Most people are capable of port forwarding, But just hanging a smallish public project out there in the open is always a dicey proposition. It honestly needs real fail2ban, probably SSL, 2FA and password complexity requirements.
We could probably make a jellyfin helper container to handle some of this. Walk people through Let's Encrypt, dynDNS, port forwarding tests, add fail2ban with a firewall, maybe even slap suricata in it.
We need to convince the project to add 2FA and password complexity requirements.
I don't know guys what do you think is it crazy? does it make sense? Would anybody actually use it?
I access my stuff via VPN. As for sharing with others, I simply don't do that. VPN is still an option though. Or temporary client whitelisting, etc.
load more comments
(5 replies)
What are my realistic security concerns with a jellyfin server that I let friends and family watch while trying to minimize the troubleshooting and steps they need to take to get started?
realistic security concerns
If you're running a binary installation of Jellyfin on your server and exposing it to the public internet, you can face significant risks:
-
Remote execution vulnerabilities might allow attackers to exploit bugs to run malicious code on your server.
-
Buffer overflows. Poorly handled data can let attackers manipulate memory, Bypass logins, touch things in the host that aren't meant to be twiddled with
-
Network exposure. If compromised, the server could become a launchpad for attacks on your network.
There might not be any vulnerabilities at this moment, but they might come in a future release. And we might not even know they exist. It's a small team of volunteers, and they'll do their best. This is just what is reasonably possible when installing the server as an application on your OS and exposing it to the Internet.
You can minimize risk with a safer setup, as someone else in the comments here mentioned (and I think they even linked to their setup)
Using a Docker container version of the app significantly reduces your attack surface. This isolates the app from your host system. If they get in, they only get into the container and whatever that container is allowed to do.
Mount your media files as read-only to prevent accidental modifications or potential malicious changes. Now that container can't do any real harm do your data.
Avoid making the container privileged. A privileged container can interact with the host system in risky ways.
Use reasonable unique usernames and passwords. If the container does manage to get compromised, they will likely be able to read usernames and passwords stored in the container.
Regularly update your container – Ensures you have the latest security patches.
Short of some massive Docker vulnerability, (which is on you to keep updated) the worst case should be public enumeration of your media, exposure of your JF users/passwords, and denial of service. Which IMO isn't very serious.
For even tighter access control, don't whitelist the entire world.
Whitelist specific IP addresses. Have users visit WhatIsMyIP to get their IP, then configure port forwarding to allow only trusted addresses. This allows the clients at their houses in without any serious hinderance, but would block them from accessing your media when they're not at their house.
If they're accessing you through a phone or PC, setup headscale or tailscale or any VPN and allow them to get to you through VPN
Amazing info, thank you for the response!
I would be very interested in an answer to this as well. Also any how to guides that would be useful for a guy whose technical high-water mark was getting mint set up on my laptop.
load more comments
(28 replies)
Every non-Free Software will betray you eventually. It's only a matter of time.
load more comments
(12 replies)
Old news, but time for Jellyfin. I made the switch a couple months ago. Some minor teething issues, but better, IMO, especially now as my family all have LDAP users and that just works.
load more comments
(38 replies)
Welp, i killed mine yesterday as it wouldnt let me stream while offline. Modem died so no Internet for me. Why do i have everything local if it dosent work while offline...
Exactly. Thats why i use jellyfin now. Try installing it alongside. For me it worked well.
load more comments
(3 replies)
load more comments
(1 replies)
In this thread:
- An OP that doesn’t understand how their network is working
- People rushing to suggest a solution that they fawn over because it’s open source. I have yet to see anyone recommend Emby.
- “Tailscale will solve all your problems!” Great - how do I make that work on an LG TV that’s 100 miles away?
- Open source has high immunity to devs making changes at the expense of user for their benefit because anti-features can be removed. Recommending another proprietary alternative here would be like saying they aught to leave an abusive partner but then recommend someone with the same red flags.
load more comments
(21 replies)
load more comments
(55 replies)
Someone else already said it and you've already swapped but I'll say it in detail:
when setting the server connection up you selected "ServerName (long string of numbers)" and not "ServerName (your IP - SECURE)"
this routes your connection through the Plex servers and makes it not a local connection anymore. this is extremely easy to do and forget you've done because it barely impacts performance
load more comments
(5 replies)
Remote, yes, they announced you need Plex pass one side or the other for it to work.
Local, no, that shouldn't happen. Your device isn't reaching your Plex server locally.
To work around the remote issue, you can VPN to your local network.
But you're better off in the long haul with Jellyfin as you're doing now.
load more comments
(5 replies)
view more: next ›