2024-08-07, 11:47 AM
(This post was last modified: 2024-08-07, 11:49 AM by raulo1985. Edited 1 time in total.)
(2024-08-04, 08:15 PM)Efficient_Good_5784 Wrote:(2024-08-04, 02:54 PM)raulo1985 Wrote: Thanks for your reply. Sorry, but what do you mean by preserving the old Jellyfin config folder? You mean the one that was in the .config folder? I understand that Jellyfin doesn’t use it anymore (and I don’t see it either), and that all the config files are now located in the etc and var folders. So I thought that backing up and restoring those two folders, there weren’t other folders that need restoring.It's a bit different when you're dealing with containers. Jellyfin will create a config folder and use that for all configuration.
In your case, you should preserve both /var/lib/jellyfin & /etc/jellyfin.
You should have your server restored by backing up those two directories and adding them back on the new install.
Thanks again. The thing is, that’s exactly what I did when I gave up on the idea of just preserving the ID and tokens. I backed up and restore those two folders (and set permissions correctly), but for some reason web based clients (like JMP) still see the reinstalled server as a different one apparently (although they do get to the log in page so I guess they recognize the server, but no auto log in).
Like I said, after restoring those two folders, the clients get to the log in page, users are correct and passwords too, and all the info and settings are preserved, but they just don't auto log in. If a full restore of those two folders didn’t work for auto log in after a fresh server install, I’m officially running out of ideas.