• 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: February 8th, 2025

help-circle


  • ohshit604@sh.itjust.works
    cake
    toSelfhosted@lemmy.worldGeo-distributed Jellyfin
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    3 days 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.



  • This software is more meant to be ran in a server environment, it’s suppose to be a replacement to subscription based photo/video cloud storage. I would not recommend you run this on a desktop you use daily as it’ll consume resources in the background slowing your desktop down, this is kinda why NAS storage systems exist.

    Once you get a grasp on the BASH shell I would suggest playing around with docker and docker compose in a headless environment (headless = no desktop environment, shell only) as there are loads of applications you can self-host over your network.