Closed meestark closed 1 year ago
Hmm additional context - I provided the full list of users into the WHITELIST_USERS field and it also failed...
Looking at the logs it looks like its complaining about your Plex credentials. Are you syncing two Plex servers? Did you include the baseurl and token for both?
Yup, both servers baseURLs are provided as well as token (the token is the same for both servers as they're both from my Account, imagine Plex01 and Plex02)
eg. PLEX_BASEURL: "http://10.10.100.40:32407, http://10.10.100.40:32405" PLEX_TOKEN: "ababa, ababa"
As mentioned, with a smaller list of users, it seems to be fine. I'm suspecting one of the users, so going through and trying to identify which user and what's unique...
Hmm that's bizarre. The whitelist user variable shouldnt affect that login process that is failing. Let me take a look and get back to you.
Managed to narrow it down - had two users, 1 who had no shares to any server, and 1 who only had shares from 1 of the servers. With those added to BLACKLIST_USERS the rest run fine.
Interesting thank you very much for finding that. I'll see if I can do a check so it doesn't fail like this and will just skip the user.
Can you try the Dev branch, i think i got a fix implemented so it will skip over generating the watch list and marking watched for the user that has no access to libraries.
I believe this is solved now per my personal testing. I created a test user on both jellyfin and plex and in plex i did not provide the user any library access. In cases like this the user does not have a token for the server as such it was causing errors. This now skips the user for getting watched and marking. This does not seem to be an issue with jellyfin based on some quick testing but if something comes up on the jellyfin side we can create a new ticket for it.
Describe the bug The process is unable to run if WHITELIST_USERS variable doesn't have anything in it
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Logs
Type:
Additional context Works perfectly fine if I provide users in the WHITELIST_USERS variable. I tried both my account in the WHITELIST_USERS, as well as just a user's account and there was no difference, successful run every time.