Re:Plex vulnerabilities being exploited in the wild to drop ...
by yegle on Monday October 19, 2026 @03:10PM
(#50156618)
Tailscale is easy to explain.
"Install this app on your Apple TV or Android TV, login with your Gmail, and let me know your email address."
Re:Plex vulnerabilities being exploited in the wild to drop ...
by financetechbro on Monday October 19, 2026 @04:51PM
(#50157883)
Yes I’ve successfully explained Tailscale to anyone that has had a corporate job and has experience having to log into a work computer VPN before accessing their work intranet
Re:Plex vulnerabilities being exploited in the wild to drop ...
by DANmode on Monday October 19, 2026 @08:26PM
(#50159819)
or has heard of anyone who has had one.
Re:Plex vulnerabilities being exploited in the wild to drop ...
by skinfaxi on Tuesday October 20, 2026 @09:46AM
(#50166367)
At least for me the issue is that most TVs don't have a tailscale app. I resolved this for my mother in law by setting up a permanent VPN to my house but that doesn't scale to all my friends.
Re:Plex vulnerabilities being exploited in the wild to drop ...
by echelon_musk on Monday October 19, 2026 @09:23PM
(#50160207)
Re:Plex vulnerabilities being exploited in the wild to drop ...
by thejazzman on Monday October 19, 2026 @09:36PM
(#50160298)
I was on this same line of thinking a few months ago when I made the mistake of switching to T-Mobile Home Internet and discovered I'd been CGNAT'd
Every time I want to share with someone I have to stop and debate if I want to possibly have to drive over to their house etc.
So here's my attempt at solving the problem: https://pixelbrite.site/en/profiles
Re:Plex vulnerabilities being exploited in the wild to drop ...
by Marsymars on Tuesday October 20, 2026 @12:58AM
(#50161522)
Can’t you use ipv6?
Re:Plex vulnerabilities being exploited in the wild to drop ...
by thejazzman on Tuesday October 20, 2026 @09:29AM
(#50166095)
yes. But can my users? maybe.
My intention is to make it work with as little friction as possible
Re:Plex vulnerabilities being exploited in the wild to drop ...
by skinfaxi on Tuesday October 20, 2026 @09:50AM
(#50166434)
This is pretty cool! Your other stuff seems cool too (esp pixel prism). Are you planning to build a business around this?
Re:Plex vulnerabilities being exploited in the wild to drop ...
by clundin22 on Monday October 19, 2026 @11:29PM
(#50161007)
I use a raspberry pi and nginx to forward my jellyfin over Tailscale. This works really well, Tailscale is low touch and nginx is battletested. Jellyfin appears as a local service to other devices and I manage the raspberry pi with NixOS which makes the setup easy and deployable. Just plug in the pre imaged raspberry pi.
Re:Plex vulnerabilities being exploited in the wild to drop ...
by falkensmaize on Tuesday October 20, 2026 @12:25AM
(#50161342)
If the alternative is dangerous exposure on the public internet, I'll choose either setting it up for them or just not sharing with them at all. Honestly I think all this widespread "family" sharing with 200 of your closest friends stuff is going to lead to another industry crackdown. I think it might be better for this stuff to stay a little geeky.
Additionally, if they try to connect from an Android TV / Fire Stick, where you can't configure a VPN (and use their ISP's modem, so no wireguard client on the router to transparently route to the subnet), what are you supposed to do?
I feel it may be easier long-term to just contain the Jellyfin daemon to only r/o access to media, putting it behind a subdomain like jellyfin.example.com, and use the dns-01 challenge via LE to only provision a wildcard cert for the domain (IE *.example.com).
Then, have nginx listen on 80/443 with a default server directive that returns 444 for any requests not to the (correct) jellyfin hostname (due to bots hammering 80/443 across the internet on webserver's direct IPs).
Its the only solution I can think of to make it easy for nontechnical users (everything just described is completely invisible to a regular client) while reducing the attack surface area of the daemon.
FWIW, with the aforementioned setup, I got 0 unauthorized requests to my jellyfin server. Just a bunch of bots hammering my IP's 80/443 ports directly with exploits for old (usually wordpress) vulns, but they were all served 444 (IE an immediate TCP connection close without nginx even responding to the request).