I started using Jellyfin a few years ago as a shared backend for my Kodi boxes (CoreElec mostly but not exclusively). I use the Jellyfin plugin for Kodi, installed from the Jellyfin repo as per official instructions. I’ve stuck to defaults/recommendations in the plugin. I did this for the WAF (wife approval factor), because otherwise none of my family ever used it. Now I get a shared watchlist and can stop on one TV and resume on another.

I’ve been running into a problem, and after extensive troubleshooting, I’m at a loss and asking for help.

The Kodi boxes do not pick up new content when it hits my server, which happens fairly regularly as I am ripping my disc collection into a format that Kodi (and the little Arm boxes) support natively. Unless I restart Kodi or the Jellyfin plugin every day or so, they do not see any new files uploaded since their last restart and if it goes long enough, even watched status falls out of sync and I have to go through the lengthy process of resyncing that entire library.

If I restart my Jellyfin service, every Kodi box immediately reconnects within a minute but still nothing syncs unless I restart the client.

Is this a known issue (Google is pretty useless in this regard)? Is there an option I can change somewhere to force the check-in to sync on a schedule? Is there another plugin that would work and still show content “normally” in the libraries, as opposed to going into another screen? Or does everyone use the Jellyfin web frame client?

Thanks.

    • Synestine@sh.itjust.worksOPEnglish
      1·
      11 months ago

      I am, yes. It came pre-installed. I even have retention days set to unlimited. The startup sync seems to work, but I hate restarting it daily. The live sync is what doesn’t seem to be working for me.

  • kaktus@feddit.nlEnglish
    1·
    11 months ago

    Sync does work for me. I only noticed, once I restart the server, the Kodi clients are no longer connected and need to be restarted too.

  • elfio@sh.itjust.worksEnglish
    1·
    11 months ago

    I’ve found myself in a similar situation. I thought it was due to jellyfin being behind a nginx reverse proxy, so I followed the docs in order to allow websockets to work, but either I did it wrong or the issue is something else. I’ll keep an eye on the post just in case someone knows the solution :)

    • Synestine@sh.itjust.worksOPEnglish
      1·
      11 months ago

      I’m not using nginx, though good to note the web socket. Mine is all local-net. The plugins auto-detect my server at its correct hostname:port at first install.

      • elfio@sh.itjust.worksEnglish
        1·
        11 months ago

        That’s interesting as it doesn’t rule out the nginx config being the the right one. Thanks for telling me :)