Cloned JellyFin instances funnies

[LeeNX]

Setting up WatchState for the first time and run into a really funny issue, where going into Tools -> Sub Users would load the page, but there was a Loading page .... I was not able to find any other issues or discussions with the same problem, but finally found out that my two test instances of JellyFin, which I had cloned from another instances, all had the same identifier.

This is not a bug with WatchState, but might be a corner case that might be worth checking for.

Also might be worth noting in the docs, how to possible fix or address this issue. In my case, stopped one of the JellyFin instances and find the device.txt file in my case config/data/device.txt and renamed it. Restarted the instances and things improved and I was able to get into the Sub Users page.

Best to do this on the less used instance as you will need to re-connect/re-create all your client logins to this instance.

Hope this helps others.

[arabcoders]

Thank you for finding this, i'll add mitigation against this while adding a backend to prevent backends from being added.

Edit: actually i cant do that as this would break 3-way sync.

I will instead add FAQ entry about it.

[LeeNX]

I think it might be related, but the backend for JellyFin instances, kept reverting to limited too.

Now that I have it fixed, I don't get the limited API key warning either.

FAQ should be good, maybe a warning if it is found. Feel like I spent a bunch of time, where my setup was broken.

Otherwise, this is freaking awesome! Thanks a ton. This can be closed, unless there is anything else worth adding?

[arabcoders]

Thanks for the tip, I've added something about it in the FAQ. If it happens frequently we may add extra warning otherwise, you are the first person to encounter this =)