2024-07-26, 05:26 PM
Hi. I experimented a little bit, started from scratch and only restored the data folder (located in /var/lib/jellyfin), which contains both the database and the device.txt file. It didn’t work, but there was a difference. Before (starting from scratch without restoring anything, so the server had a new ID), the clients showed that there was a server available but couldn’t connect to it (you had to do it manually). Now it shows a couple of items of the GUI, but it keeps loading forever (and again, if you manually log in, everything works). That tells me that you need more than just the device.txt file and the database (for the tokens) for the clients to keep logging in automatically after a full server reinstall (because both are located in the data folder, which I restored).
Then I tried again and restored all the contents of the /var/lib/jellyfin folder and the /etc/jellyfin folder (a full backup and restore), and to my surprise, the same thing happened again (the clients remain stuck on loading, and you can’t use them unless you log in manually). I wasn’t expecting that since it was a full backup and restore, but then I realized that I backed up and restore everything from both folders, except the contents of the /var/lib/jellyfin/.aspnet/DataProtection-Keys. They weren’t backed up because of permissions (stupid thing from my part, I didn’t realize I didn’t back up those files).
Bottom line is, after a full backup/restore from both /var/lib/jellyfin and /etc/jellyfin, clients are still unable to log in automatically after a server reinstall. Could those files (the ones inside the DataProtection-Keys) be the missing part of this puzzle? What are those files for? They are the only files missing from the full backup/restore, and I understand that after a full restore all the clients should log in automatically since the server ID and tokens are preserved. Are those files related to user log in info? If not, I don’t have a clue why my clients aren’t logging in after the server reinstall (and FYI, permissions are set correctly after the restore, so that shouldn’t be the issue).
Any thoughts? Thanks in advance.
Then I tried again and restored all the contents of the /var/lib/jellyfin folder and the /etc/jellyfin folder (a full backup and restore), and to my surprise, the same thing happened again (the clients remain stuck on loading, and you can’t use them unless you log in manually). I wasn’t expecting that since it was a full backup and restore, but then I realized that I backed up and restore everything from both folders, except the contents of the /var/lib/jellyfin/.aspnet/DataProtection-Keys. They weren’t backed up because of permissions (stupid thing from my part, I didn’t realize I didn’t back up those files).
Bottom line is, after a full backup/restore from both /var/lib/jellyfin and /etc/jellyfin, clients are still unable to log in automatically after a server reinstall. Could those files (the ones inside the DataProtection-Keys) be the missing part of this puzzle? What are those files for? They are the only files missing from the full backup/restore, and I understand that after a full restore all the clients should log in automatically since the server ID and tokens are preserved. Are those files related to user log in info? If not, I don’t have a clue why my clients aren’t logging in after the server reinstall (and FYI, permissions are set correctly after the restore, so that shouldn’t be the issue).
Any thoughts? Thanks in advance.