Jellyfin wont load to UI

[TheDreadPirate]

That solution only applies to Windows servers.

This is a bare metal linux server, right? Or is this a linux VM running on a Windows machine?

[kira100000]

I do remember getting a root file system requires manual fsck error right before all this happening, I ran fsck and everything seemed to come back fine. On restarts I havent recieved that error again.

Its a bare metal linux server.

Now that Im thinking about it that error happened exactly before realizing I couldnt connect. File system seems okay though, network share is still recognizing the mount and I can move files around ect..

[TheDreadPirate]

Stop the Jellyfin container, then run "docker system prune -a", then start the jellyfin container again.

[kira100000]

Stop the Jellyfin container, then run "docker system prune -a", then start the jellyfin container again.

after waiting a bit after doing this I can get to the jellyfin login now.. but logging in gives invalid user and password when I know its not

edit: getting crazy logs in the docker now https://pastebin.com/3TDH143Q

[kira100000]

No idea what really happened. removed the container and remade it, had to make a new user, re scanned everything to library and now things are peachy

[TheDreadPirate]

Did your container have host volumes for /config and /cache? It sounds like when we pruned docker it purged all your Jellyfin data. Which would only happen if you did not provide permanent storage for /config.

[kira100000]

Did your container have host volumes for /config and /cache?  It sounds like when we pruned docker it purged all your Jellyfin data.  Which would only happen if you did not provide permanent storage for /config.

I honestly dont know the answer to that. I myself did not set that up so unless the yams installer did that for me the answer would be no.

unless youre asking if I copied the config and cache folders before hand which then the answer would be yes.
but i guess i didnt replace them before going back to jellyfin

[TheDreadPirate]

If you COPIED the original config and cache folders, vs moving them, then my assumption that YAMS is NOT providing a permanent location for them is probably correct.

If you have access to the docker compose that YAMS is using, you could modify it to add permanent storage for /config and /cache.