33
submitted 9 hours ago* (last edited 3 hours ago) by xana@lemmy.zip to c/selfhosted@lemmy.world

Hi TCP users,

Currently, I have a homelab server that runs Jellyfin with direct access to local media content and a reverse proxy point to it. While it works well for people in Europe (where the server is), it is quite slow for some of my friends who are living in Asia. I am having some options in mind:

  • Hire a VPS in Asia and set up another Jellyfin instance there. This works but I don't really want to have two Jellyfin instances with two databases and also accessing to local media content will be curbersome to manage.
  • Hire a VPS in Asia and set up a CDN but I am not sure if it will ever work with Jellyfin ?

So I would like to ask do you know any things about this and any idea to improve this situation ?

Thank you very much!


Edit: Thanks for all of your response. Based on my experience, I think the slowness is caused by the fact that there are too many hops to jump through before reaching the final client. So I think I will try to do several things:

  • Try to optimize my upload speed, it is fast enough but not very stable recently so it could have some impact
  • Set up a second Jellyfin instance and sync a part of my library there for my friends.
top 17 comments
sorted by: hot top new old
[-] frongt@lemmy.zip 1 points 32 minutes ago

Define "slow". Pages hang before loading? Or it often stops to buffer a stream?

[-] glitching@lemmy.ml 4 points 4 hours ago

don't know what "slow" means in your case, but jellyfin clients have a buffer setting and increasing it should improve things for them.

[-] Flax_vert@feddit.uk 2 points 4 hours ago

I am in basically the same situation as you and my single asian user has no issue with it

[-] Ptsf@lemmy.world 7 points 7 hours ago

Tailscale, headscale, or something along those lines may help optimize the route but as others have said to resolve this is an actual fashion you'd need a cdn which requires significant geo-redundant hardware which comes at a pretty significant cost. That being said I think your friend has a good shot if you implement the former.

[-] johnnixon@lemmy.world 1 points 1 hour ago

I was trying to stream my Jellyfin server on vacation..Over Tailnet I couldn't reliably stream anything. Over VPN it was as good as local. I can't believe it's just a routing issue but I wasn't proxied so it should have been the same. So a VPN for one user might fix the issue. The headaches of segmenting the network on that VPN are another problem even if the hardware/router is capable but doable.

[-] just_another_person@lemmy.world 18 points 8 hours ago

You're describing a CDN. You can't afford it.

I'd look more into boosting whatever your uplink is versus trying to distribute to localized users.

[-] Atherel@lemmy.dbzer0.com 9 points 7 hours ago

The uplink isn't the problem as it works for viewers in Europe.

[-] just_another_person@lemmy.world 4 points 6 hours ago

Uplink is exactly the problem. Not sure why you think otherwise. The internet doesn't work by multicast.

[-] Atherel@lemmy.dbzer0.com 1 points 4 hours ago* (last edited 4 hours ago)

Maybe we don't talk about the same. The uplink at OPs router isn't the problem, there is enough upload speed so that others in Europe can stream. Users in Asia don't have enough bandwidth, so there's a bottleneck somewhere in between.

And yes, a VPN could help by routing the traffic through other hops, but chances are that it doesn't help or even make it worse, but it's worth trying.

[-] frongt@lemmy.zip 1 points 34 minutes ago

It's probably not bandwidth but latency and packet loss that's the problem.

[-] just_another_person@lemmy.world 2 points 2 hours ago

Bandwidth does not degrade over distance. That's not how that works...

Again, I'm confused on what you're suggesting the actual issue is here.

[-] ExcessShiv@lemmy.dbzer0.com 2 points 1 hour ago

If the uplink bandwidth is more than sufficient for users in Europe, and it doesn't degrade over distance, then why is the same uplink not enough for the exact same thing in Asia?

[-] Brkdncr@lemmy.world 16 points 8 hours ago

Even large streaming services drop their servers close to the users to make the experience good. They just do better at scaling.

You could federated authentication so only one ldap service is maintained. You could also sync media from one device to the other so you don’t need to manually update both.

[-] non_burglar@lemmy.world 12 points 9 hours ago

You unfortunately cannot solve this yourself, this is where 800lb gorillas like akamai outclass self-hosted.

Netflix alone has many thousands of isps participating in Open Connect alone, these providing CDN peering points all over the world and making Netflix only a few hops away for more end users.

[-] ohshit604@sh.itjust.works 2 points 6 hours ago* (last edited 6 hours ago)

You don’t necessarily have to host another Jellyfin instance, I would find a server somewhere in-between the middle of your current Europe server and your Asian homies and setup a reverse proxy there and point it to your current Jellyfin instance.

The only hassle with this is you’re going to need a way to expose Jellyfin to it, a VPN would prevent port forwarding 443, perhaps split tunneling?

Not the most elegant solution but at least this way you can make an attempt at optimizing the connection.


Edit - (if you wanted to go the second Jellyfin instance route): Could also copy your current database to the second server, host a second Jellyfin instance and have something like sshfs or sftp sharing the directory to your media library, reverse proxy it as something like asia-jellyfin.your.domain and keep it separated from your Eu server.

[-] TheHolm@aussie.zone 7 points 9 hours ago

IMHO Jellyfin is processing everything it sent to clients. So I do not think it possible to put it behind SDN( may be it possible if server side transcoding is off) Please define slow. Slow on what part? It should be like 250ms RRT to your server which is not much for web-based apps.

[-] performation@feddit.org -2 points 8 hours ago

This may be completely untrue but maybe the remote users could get a vpn with a server near yours? Without having the slightest idea that it does I could imagine it could help.

this post was submitted on 05 Feb 2026
33 points (94.6% liked)

Selfhosted

55917 readers
509 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS