2024-08-14, 12:25 AM
2024-08-14, 12:33 AM
My last idea: Do you have any custom CSS or themes? I can't think of anything else other than Jellyfin is corrupt in so way.
2024-08-14, 12:36 AM
(This post was last modified: 2024-08-14, 12:44 AM by keduncan3. Edited 1 time in total.)
(2024-08-14, 12:33 AM)TheDreadPirate Wrote: My last idea: Do you have any custom CSS or themes? I can't think of anything else other than Jellyfin is corrupt in so way. I do. I'll try removing that and see. I believe I'm using the plugin for themes. **Edit** I was wrong. I was using CSS, not skin manager. I removed the CSS and attempted again with no change. I supposed it's time to wipe and do a clean install.
2024-08-14, 04:06 AM
(2024-08-11, 10:11 PM)TheDreadPirate Wrote: On the original Jellyfin instance, under the parental control settings did you add tags under "Allow items with tags"? Just to come back and close out the issue in case anyone else has this issue, I copied my config/cache folders to another directory for the fresh install (previous folders were under /usr/docker/Jellyfin/cache, new ones are under /usr/docker/Jellyfin1/cache). Installed new container running Jellyfin and all is well. Library, images, metadata, etc is all there. User info is still there and voila, the users are able to see movies now on LAN and via external access. I'm not sure where the hang up was, I guess something went awry when I updated to the newest version of Jellyfin.
2024-08-14, 01:46 PM
Ah, ok. So in addition to all your permanent files in /config and /cache, there is a VFS (virtual file system) for the container's "OS". Something must have been corrupt or something in that VFS.
If this ever does happen again you can try this. Stop the container then open a terminal window. Code: sudo docker system prune -a Then restart the container and it should re-pull the image and recreate the container and VFS. Without having to move around your config and cache folders.
2024-08-14, 05:32 PM
(2024-08-14, 01:46 PM)TheDreadPirate Wrote: Ah, ok. So in addition to all your permanent files in /config and /cache, there is a VFS (virtual file system) for the container's "OS". Something must have been corrupt or something in that VFS. Thank you! I appreciate all your help! |
|
|