Selfhosted

62094 readers

165 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Geo-distributed Jellyfin (lemmy.zip)

submitted 7 months ago* (last edited 7 months ago) by xana@lemmy.zip to c/selfhosted@lemmy.world

30 comments fedilink hide all child comments

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

[–] ohshit604@sh.itjust.works 2 points 7 months ago* (last edited 7 months 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 your Eu Jellyfin to the new server, 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.