Wireguard or tailscale are much better ways of accessing jellyfin from outside your network.
Comment on Round Two: Can I manage to set up Jellyfin correctly this time?
compostgoblin@lemmy.blahaj.zone 2 days agoThanks for the tip! I’ll back the refresh rate off to be safe.
I’m not sure I entirely understand your concern about putting Jellyfin on the internet. A large part of my interest in selfhosting is being able host my own music library, my own cloud storage, etc, and access it as an alternative to Spotify or Google Drive. Doesn’t that inherently mean that they need to be on the internet, if I want to be able to access them when I’m away from home?
My goal has been to find a way to do that safely, but if that’s not possible, that’s good to know too, so I don’t keep trying to do the impossible.
AbidanYre@lemmy.world 2 days ago
compostgoblin@lemmy.blahaj.zone 2 days ago
What if I want a bunch of people to be able to log into my library via Finamp?
cyberwolfie@lemmy.ml 1 day ago
I use Nginx Proxy Manager and whitelist my remote users. They all have static IPs though, so its a workable solution for me.
Before I used a whitelist I would go through the access logs, and could never find any attempts to exploit the endpoints - only some random bots trying to find some admin page assuming it was another service. Not saying you shouldn’t take it seriously, but you are likely not subject to these attacks the moment you expose it.
That said, there is a discussion about these endpoints on their repo. At some point they will be fixed (my impression is that they are hampered by legacy Emby code). When they do, you could do this more securely.
frongt@lemmy.zip 2 days ago
Provide them with VPN access. If that’s too much for them, then they don’t get access. Tough. On the scale of security vs convenience, that’s nothing.
If you really really want, you should at least see if you can put a WAF in front, and put the server itself somewhere it doesn’t have access to the rest of your network (a DMZ) so that if and when it gets hacked, it doesn’t compromise the entire network.
FreedomAdvocate@lemmy.net.au 2 days ago
You use plex instead.
Auli@lemmy.ca 14 hours ago
What vulnerabilities? Sure there are some but nothing massive that I have seen. Care to post them.
ExperiencedWinter@lemmy.world 2 days ago
I highly recommend Tailscale, you can share machines/services with unlimited friends on the free tier, and all of the actual auth stuff is handled by someone who isn’t me.
dogs0n@sh.itjust.works 1 day ago
It’s honestly just a matter of how much risk you are comfortable with for using jellyfin on the open internet.
(If i remember correctly:) The unauthenticated routes thing can only be used for streaming your content without a login (if you can guess the contents ids on your server I believe).
In my opinion, it’s not worth the hassle of using a vpn because I don’t think this risk is worth mitigating with one.
But everyone has their own personal risk assesment of course.
frongt@lemmy.zip 1 day ago
Yes, those are the known vulnerabilities. We don’t know how many unknown vulnerabilities could be discovered in the future.
Auli@lemmy.ca 14 hours ago
And are these the ones they let people see what media I have or are there any serious ones?
dogs0n@sh.itjust.works 1 day ago
Unfortunately no software exists that is fully perfect in this regard (any program could have multiple bugs just waiting to be found), but jellyfin being open source puts it in a better situation for finding vulnerabilities sooner.
ITGuyLevi@programming.dev 1 day ago
At least we are more likely to hear about them than we would for PMS. Quickest way to find vulnerabilities is to have as many eyes as possible on it, if you only let the 20 devs you employ look a lot can be missed. Just my opinion though.