I think people over blow how dangerous it is. Or maybe its better most people dont. I don’t know I know the issues and I take measures to mitigate them. Then if someone gets in they would be limited to vlan. And if somebody gets out of that good wasted so much effort for nothing since I have nothing that would be worth that much trouble.
And before someone says identity pretty sire that has been in so many other leaks overt the years the information is pretty old.
Read-only, rootless container with only the cache/transcode/config folders mounted RW+noexec - ideally both with a volume size limit.
Reverse proxy only the absolutely minimal ports needed, with some security measures (e.g. crowdsec transparent proxy, hooked up to both your firewall and reverse proxy to block malicious actors.
Just throw a wireguard tunnel on your router and call it a day.
If ya gotta host public put a dedicated proxmox host on its own port on your router, make it a trunk line, and give every VM its own subnet/VLAN/Firewall ruleset.
That’s pretty much the number one reason people say they won’t move to Jellyfin - the ease of public access.
Even though exposing your shit to Internet is a terrible idea for most people.
I think people over blow how dangerous it is. Or maybe its better most people dont. I don’t know I know the issues and I take measures to mitigate them. Then if someone gets in they would be limited to vlan. And if somebody gets out of that good wasted so much effort for nothing since I have nothing that would be worth that much trouble.
And before someone says identity pretty sire that has been in so many other leaks overt the years the information is pretty old.
Even without data compromise or pivoting, they can still mine crypto on your hardware, launch a ddos, spam email, do botnet stuff, or host CSAM.
Not if your Jellyfin is set up correctly.
Read-only, rootless container with only the cache/transcode/config folders mounted RW+noexec - ideally both with a volume size limit.
Reverse proxy only the absolutely minimal ports needed, with some security measures (e.g. crowdsec transparent proxy, hooked up to both your firewall and reverse proxy to block malicious actors.
Just throw a wireguard tunnel on your router and call it a day.
If ya gotta host public put a dedicated proxmox host on its own port on your router, make it a trunk line, and give every VM its own subnet/VLAN/Firewall ruleset.
That’s fine for your personal remote access but that doesn’t help your 80 year old mother in law watch videos of the grandchildren on a Roku.
Been thinking of throwing together a set top box with everything made up for my grandfather so he can stream stuff from my jellyfin setup.
I just need to find an ezpz enough to use frontend.
Slap a vpn on her computer or but a shitty dell from good will. Point the Roku at that and forward the traffic…?
Like this is a solvable setup and forget about it for the next 5 years. Sort of set up.
WG works for us, but isn’t scalable once it comes to sharing. It would provide too much friction for a lot of people
I manage it with netbird.
Just have em install netbird, if it’s on they can connect to my website. If it’s off they can’t.
It’s literally three steps for each person, there’s ways to make this easy. It just requires the host to put in the leg work
It’s really not. If people are too lazy to install one VPN app and import the tunnel config, then they can pay for paid streaming instead.