this post was submitted on 03 Apr 2025
41 points (97.7% liked)

Selfhosted

45411 readers
314 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
41
Moving from Cloudflare tunnels for media streaming, first plan didn't work out due to double NAT (lemm.ee)
submitted 1 day ago by chriscrutch@lemm.ee to c/selfhosted@lemmy.world
20 comments fedilink hide all child comments
 

I have several services on my home server, most of which I access using Tailscale, and it works great. I had a couple services on Cloudflare tunnels in order to access them from devices that I can't put Tailscale on.

Plex is going to start charging for remote access. So I figured now would be the time to migrate to Jellyfin. But using Jellyfin on Cloudflare tunnels is against their TOS. I have a Roku TV at a remote location that I use to watch Plex. I won't be able to do that anymore. And I can't put Tailscale on it to serve Jellyfin that way.

I was going to set up Nginx Proxy Manager to use my domain name for Jellyfin so I didn't have to use Cloudflare tunnels. But in setting that up I found out that my ISP is double NATting me, and I haven't been able to find a way around it.

So I'm left with two options: 1) buy Plex Pass so I can continue to stream remotely; or 2) get a VPS, run Tailscale and NPM on it and switch to Jellyfin.

I'm looking for a sanity check to make sure the VPS thing would work the way I think it would. If it's running Tailscale then the double NAT would be a non-issue, correct? Is there another option that I haven't thought of yet? Which of the two options would you choose?

you are viewing a single comment's thread
view the rest of the comments
[–] SirMaple__@lemmy.ca 20 points 1 day ago* (last edited 1 day ago) (10 children)

Do not. I repeat do not expose Jellyfin to the internet. It has too many security issues to be directly accessible from the internet.

I use Jellyfin and only access it over WireGuard. I have a mesh setup between the routers at a few family members houses.

If you have absolutely no other way then to expose it to the internet you need to make sure that you whitelist only the approved IPs in your VPS firewall and block everything else.

[–] Max_P@lemmy.max-p.me 11 points 1 day ago (2 children)

I keep hearing claims that it's not secure enough to be exposed on the Internet, but I can't seem to find anything about unauthenticated vulnerabilities. It's got a fair amount of CVEs but they all seem to affect when you're an already authenticated user, mainly to XSS an admin as a regular user or the likes.

It's written in C#, and publicly all you can do is pretty much attempt to log in, this feels like it should be pretty sane compared to some other PHP crap I run.

Do you have any examples of previous exploits or anything else to be concerned about?

[–] SirMaple__@lemmy.ca 1 points 22 hours ago (1 children)

https://github.com/jellyfin/jellyfin/issues/5415

[–] Strit@lemmy.linuxuserspace.show 8 points 22 hours ago

Most of the relevant issues they link to has been closed and/or dealt with.

load more comments (7 replies)