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!
Maybe we don’t talk about the same. The uplink at his 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.
It’s probably not bandwidth but latency and packet loss that’s the problem.
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.
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.
Exactly, bandwidth doesn’t degrade over distance, so why would the uplibk bandwidth be the issue for Asia when its fine for Europe.
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?