Updated and now can't add library/files

[private_wombat]

I've been using JF for about 9 months successfully. I installed and ran it on my NAS via Synology Container Manager. Last time, I did not create a user or do anything special to give JF permissions on the NAS folder besides the basic setup in Synology. I decided to update the container to the newest version last night. After the update, JF lost my old library and has not been able to successfully add one since. When I add a new library JF is able to find the correct folder in the popup but nothing is added afterward. As I mentioned, I never created a specific user on Synology for JF previously, but I've seen threads since this issue popped up that suggest that's the problem. Very strange. I'm attaching screenshots of my setup and including logs as well. 


   
               
                       


  JF Logs.txt (Size: 68.89 KB / Downloads: 7)

[bitmap]

I decided to update the container to the newest version last night. After the update, JF lost my old library

I would just like to point out that you did not persist any of your Jellyfin data in the Docker setup you provided. Those environment variables listed (i.e., JELLYFIN_*) represent folders. If you do not map them, they are destroyed when you remove the container -- which happens when you update the container. I think you need the DATA_DIR and CONFIG_DIR, but the DATA_DIR is top-level, so the rest should follow. That needs to be mapped the way you mapped your media in the volumes section.

Code:

- /path/to/store/jf/data:/config

I would start fresh (which you're doing already) and map this volume, see what happens.

[private_wombat]

I decided to update the container to the newest version last night. After the update, JF lost my old library

I would just like to point out that you did not persist any of your Jellyfin data in the Docker setup you provided. Those environment variables listed (i.e., JELLYFIN_*) represent folders. If you do not map them, they are destroyed when you remove the container -- which happens when you update the container. I think you need the DATA_DIR and CONFIG_DIR, but the DATA_DIR is top-level, so the rest should follow. That needs to be mapped the way you mapped your media in the volumes section.

Code:

  - /path/to/store/jf/data:/config

I would start fresh (which you're doing already) and map this volume, see what happens.

I'm sure I messed that up, I'm a total noob and I have no idea what I'm doing. So that is something I should have said at the outset. I am honestly not even sure why this is coming up now as the last time I installed I didn't do anything with mapping DATA_DIR and CONFIG_DIR as it worked right out of the gate with no tweaking/config changes. 

When you mention mapping DATA_DIR and CONFIG_DIR with the code snippet you pasted, where do I put that? I'm sorry to be so stupid about this, I'm genuinely lost as to why this install/update is so different than last time. Really appreciate your help.

[bitmap]

Your screenshot with "Volume Settings" -- add folder, use the folder location on your server that you want config files stored. Note that this can get large. In the second field, just put /config.

[private_wombat]

Your screenshot with "Volume Settings" -- add folder, use the folder location on your server that you want config files stored. Note that this can get large. In the second field, just put /config.

I'm back up and running with a new fresh install of Jellyfin. These are the container settings for the data. I created a new folder to store that and have it set up correctly. Should that solve the issue of data not persisting after an update? 


   

[TheDreadPirate]

That should work, but a bunch is unnecessary and there is still the issue of config and cache not being separate. The JELLYFIN_DATA_DIR variable should be /config. And the volume for Jellyfin's data should have separate volumes for config and cache. Like this.

Code:

/volume1/MediaP/jellyfin/config:/config:rw
/volume1/MediaP/jellyfin/cache:/cache:rw

Your volume for your media can be whatever you want on the container side.