answered: plexapi.exceptions.NotFound: (404) not_found. why? #1037
-
|
Hello, with tihs config for shows: I get the errror Thank you! |
Beta Was this translation helpful? Give feedback.
Answered by
chazlarson
Sep 17, 2022
Replies: 4 comments 3 replies
-
|
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thank you very much, looking at the logs, I see most of the collections now have that error. do I have to enter a numeric library iD anywhere in the config? More error log: |
Beta Was this translation helpful? Give feedback.
-
|
You shouldn't have to enter those manually, no. The Plex API should be providing them to PMM. My guess here is that for some reason Plex is not doing so and PMM isn't prepared for this case ["None" is the default "this variable has no value" in Python]. Chances are this is a follow-on from some earlier failure, or there's some internal Plex issue? Can you provide the entire meta.log that shows this problem? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thank you very much for your help! It seems, the cause was here to find:
It seems to be fixed with a new token. Thanks again for explaining and pointing to the right direction! |
Beta Was this translation helpful? Give feedback.
Answer selected by
meisnate12
-
|
OT: This topic is answered, but it is not possible to mark my own reply as a suitable answer.... so I edit the title to "answered: ...." |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
From my endurance of wasted time, it seems this is due to a change in the latest release of plex server that chokes when pmm queries for a list of items with a new "tag" that has not been used before and is not in the plex database. I went way around the block with trying different versions of pmm and plex and dinking with my config to no end. I did find a workaround and reverted all my stuff back to the way it was and everything is working great now. Now, if you have your pmm trying to create "new" collections where items are tagged with "new" tags, then it chokes. However, if you delete a collection and then add the same one back, the old tag still exists in the database so it's ok. This was weird cuz i could delete all the collections and then re-run pmm and all my old, previously used/created collections would be re-created no problem. But - if i wanted to add a new, never before seen collection, it would choke - cuz that "tag" was never in the database. The simple workaround is to edit the info on any movie using the gui and add a collection tag matching the one your pmm wants to create. That manually adds that tag to the database and then pmm can use it to populate the new collection without any issues. UGH! |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
That's an issue in Plex 1.32.7 which is addressed in 1.32.8, and in that case the failure is a 500 Internal Error, not the 404 described here. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You shouldn't have to enter those manually, no. The Plex API should be providing them to PMM.
My guess here is that for some reason Plex is not doing so and PMM isn't prepared for this case ["None" is the default "this variable has no value" in Python].
Chances are this is a follow-on from some earlier failure, or there's some internal Plex issue?
Can you provide the entire meta.log that shows this problem?