35
submitted 11 hours ago* (last edited 38 minutes 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.

Edit: Slow here means both slow page loading and slow buffering.

you are viewing a single comment's thread
view the rest of the comments
[-] frongt@lemmy.zip 2 points 2 hours ago

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

[-] Atherel@lemmy.dbzer0.com 1 points 56 minutes ago

Latency shouldn't be a big problem if it doesn't have massive spikes. Packet loss could be a problem, seems like Jellyfin doesn't have an option zu increase the buffer size which may help. Or the problem is in combination with transcoding.

this post was submitted on 05 Feb 2026
35 points (94.9% liked)

Selfhosted

55917 readers
480 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