What if I’m using my pi hole with a static DNS address?
Comment on Plex ending support for Watch Together
accideath@lemmy.world 6 days agoNot without additional configuration. You’ll need to forward jellyfins port in your router and get a dynamic DNS address. That’s not hard to setup though and there are good free dyndns providers like duckdns.
SkyezOpen@lemmy.world 6 days ago
accideath@lemmy.world 6 days ago
That’s only local (unless you‘ve set up your pihole to be accessed from outside your home network already). Locally you can easily access jellyfin from any device
For remote access to Jellyfin you will need your public ipv4 address or a domain that points to it. Since in most cases your public ip isn’t static (unless you specifically pay for that), you’ll need a dynamic DNS address that regularly updates the ip address your domain points to. In case of duckdns you’d have a url like example.duckdns.org that always points to your ip.
If you are unlucky however and only have a public ipv6 address (Dual Stack Lite; highly depends on where you live and what provider you have). I haven’t found an easy free solution to still getting remote access. The easiest I’ve found is getting a domain from cloudflare and using their tunnel. Worked well and I happened to have a domain already. Streaming media via Cloudflare’s tunnel is technically against their tos though.
There are probably more elegant solutions but I have switched to a different provider since, which does offer an ipv4 address so I didn’t need to look into that any more.
possiblylinux127@lemmy.zip 6 days ago
Don’t expose Jellyfin to the internet
smiletolerantly@awful.systems 6 days ago
Why not? Have had it accessible via the Internet for 4+ years without incidents
possiblylinux127@lemmy.zip 6 days ago
What makes you so sure you haven’t been breached?
smiletolerantly@awful.systems 6 days ago
Proper precautions and monitoring.
accideath@lemmy.world 6 days ago
Well, I do want to actually use it though and have my friends be able to use it just as well.
possiblylinux127@lemmy.zip 6 days ago
You really don’t. There are plenty of other solutions. If nothing else you could whitelist there ISP instead of allowing all traffic.
accideath@lemmy.world 6 days ago
What solutions? Especially what solutions that don’t cost me money and are not overly difficult to implement?
riquisimo@lemmy.dbzer0.com 6 days ago
Why not? What precautions would you need to take before doing so?
DreamlandLividity@lemmy.world 6 days ago
The easiest and most secure solution is probably tailscale. Just VPN into your local network instead of exposing Jellyfin to the internet.
An alternative I am using is Caddy reverse proxy with Authelia for authentication. So I have to log in to Authelia before I can access Jellyfin. Beware though, it took me like 2 days to properly configure Authelia. It is rather complicated.
possiblylinux127@lemmy.zip 6 days ago
Also you could use SSH that’s been properly secured
Spuddlesv2@lemmy.ca 6 days ago
This should not be downvoted. You should not expose anything straight to the internet unless you know what you’re doing. Use a simple service like Tailscale to create a locally accessible VPN.
riquisimo@lemmy.dbzer0.com 5 days ago
“Know what you’re doing”
And
“Forwarded a port to jellyfin”
Surely has some overlap. You want to open other ports, you want to make sure permissions are properly set on the host machine… What else? HTTPS/SSL to avoid someone in the middle grabbing your password and accessing your media?
Regardless, I’ll look into tailscale. A VPN would have lots of other uses, as there are other applications I would like to use remotely that I don’t want to expose to the internet.
Spuddlesv2@lemmy.ca 5 days ago
By “know what you’re doing” I mean “understand the consequences”. Anyone can follow a guide that tells them how to open a port on their router. Understanding that in doing so they’re potentially allowing every malicious actor into their home network is not so straightforward.