Please be VERY careful of the term “SSL 3.0”
Plex stopped using SSL 3.0 some years ago and is using TLS. There was a big announcement about the transition.
They key issues I’ve found/confirmed myself so far are:
The API as they have described
Wrongful returns
There was one http (not https ) call. Everything else is https
Are you aware of any progress being made to fix theTVDB lookup problems? I just installed a new qnap server and it doesn’t find any TV show metadata. My other two servers have been operational for some time on a workstation and on a PR4100. I just noticed when just forcing an update of metadata for a show to see what would happen on the workstation that it couldn’t find what it already had. Either the Plex connectivity is not working or the database isn’t providing the data. I’m going to see if I can copy my metatdata from the workstation to the qnap nas for the shows but because it is probably quite cryptic it may be a problem. The qnap nas, a TVS-672xt, found only one show, and only the pictures, nothing else out of over 50 shows. When I do manual lookups and replace titles directly from theTVDB, it still doesn’t find them.
I am very much aware of investigation, testing , and overall progress being made on both sides.
We have already found the root cause.
We found a couple points within PMS where we can do better with API V3 return codes and are already on it.
We are single-threaded at this point pending the next progress point from TheTVDB.
And this is the best answer, folks. We shouldn’t be trying to hack our servers to get them to work with TheTVDB’s v3 API.
When the team has a tested and working fix, it will be released to the greater community. Other workarounds might be functional in the short-term, but your mileage is going to vary and could lead to other issues.
Was having issues with TVDB V3 giving errors with artwork a few weeks back using MCM changed to V2 and all was ok until yesterday when it says episode doesn’t exist so when back to V3 and retrieved metadata, but still having issues with Plex
I know not to expect TV show artwork right now, but is this issue also causing my episodes to NOT display names? Everything is coming up “Episode #” now instead of displaying the name of the episode.
The error return codes are not as currently expected.
The agent, as currently fielded in PMS, does not know how to deal with these codes.
Instead of recovering and getting as much as it can, it falls out the bottom of the poster logic, retrieving only the textual fields, actors, and actor photos.
Since this analysis, TVDB continues to change. PMS is, at present, static.
The Agent code is resident in PMS. This will unfortunately mandate an updated version.
Behind the scenes, speaking entirely hypothetically, it would not surprise me to see more of PMS’ agent logic relocated to the plex servers. A large portion exists there already.
Please do understand and remember, I am Customer Support and cannot officially speak for Engineering. I understand the nature of the problem. I, as an engineer in my own right, can see multiple solutions. Neither we, nor I, will have any information about the chosen final solution until the work is complete.
For those on older PMS versions, will just updating the agent code by side loading it in be enough or is there actual changes being made to the server? I’ve been using an older version currently to maintain access to plugins temporarily…
edit: it seems in the time since i walked off before clicking submit chuck replied.
There is no way to predict the impact of Agent changes on older releases without a complete and thorough regression design review and full regression testing.
I would not expect Plex Engineering to allow the agent to be cut & pasted from one version to another. Such a configuration is outside the scope of reasonable software control, QA, and Support.
While technically, a good developer could make a lot work, there are currently threads in the forum where some are attempting to modify the existing. None of them are meeting with success.
This having been said, the likelihood of successfully transplanting new code into an old release is unlikely .
I, as CS, must also state, I cannot support any system which was so modified. I cannot deal with all those unknowns outside my control.
By all means, take your time. I’ve already for the most part, worked my way around it anyways with a small python script and one of the many tvdb proxies. thanks for the reply chuck.
Sorry new to the forums. Is ChuckPA a member of Plex dev team? If so @ChuckPa no rush or anything but when can we see a fix? Also how will it affect our existing library. If i have to rescan everything it would suck a lot. I just want to ask so I have some expectation on how to proceed. Sorry i am not a CS major or anything so i have no idea what is happening. If this change would require full library alterations, I am concerned over the reliance of thetvdb if it would be this finicky? If it won’t affect the existing library, then just ignore everything i have just said and take your time fixing it.(reasonable amount of time) don’t come back in a year and tell us you have a fix LOL T.T
There is NO FIX. Stop. Wait it out.
One false step and you’ll have ZERO TV Show metadata - and THAT would stand atop the suck podium taking the GOLD.
Change the tracking on the Locked and Pinned Thread at the top of the forum. When there is something new to report - it’ll be there.
In the meantime - meditate or watch something. Don’t start hitting buttons trying to fix a problem there is NO solution for. Yet.
ONE thing I DID do:
Settings/Scheduled Tasks
I UN-Ticked/Disabled both functions that refresh metadata automatically.
3 Days
and
Periodically
Until Further Notice. I don’t need any ‘automatic surprises’, don’t know if either would cause one, but don’t want to find out.
I don’t think they were talking about rescanning everything now. before the bit you quoted they said
but when can we see a fix? Also how will it affect our existing library.
So, it sound to me like they were asking whether, once this is actually fixed, this will require us to rescan everything in order to correct the metadata.
That is something I’d also like to know, since I’m currently adding some episodes to my library and, if we will need to do that, I might just stop and wait until it’s fixed.
Quick question, in other threads with tangential or related issues, you close that thread and refer them here.
However, in this thread, you state “Tangential or possibly tangential issues should be discussed in a new thread . When relevant information is discovered, that information be boiled up and posted here as supplemental information.”
Myself and others have noted that even when reverting to using the moviedb api, we’re noticing that once Plex matches the name of the show via tvdb, it skips over the show. I hope I worded that right. Is there info on a workaround floating around out there for this?
I had a server/hardware failure over the weekend and just got everything back up and running - thought all this silliness was a misconfig on my end. Good to know it’s not.