TVDB Removing legacy SSL support - TV Metadata Failures now from Plex

This morning I noticed that some metadata is failing to download for TV shows from TVDB. On investigation I see errors like the following in my logs …

Metadata /system/agents/media/get request failed with code: 404: http://127.0.0.1:46057/system/agents/media/get?guid=com.plexapp.agents.thetvdb%3A%2F%2F71117%3Flang%3Den&mediaType=2&url=metadata%3A%2F%2Fposters%2Fcom.plexapp.agents.thetvdb_61ad11a1427ab8c94b7d2621cb23f85caadf6ef3

Looking into it some more I found this post on TVDB forum which could be a factor.
https://forums.thetvdb.com/viewtopic.php?f=3&t=61687

Would someone from the plex team take a look when they can to see if this is the problem and recommend a solution.

5 Likes

What is the version of your PMS?

I’m running Version 1.18.4.2171 on fedora 31 64bit – plexmediaserver-1.18.4.2171-ac2afe5f8.x86_64.rpm

Same trouble, & i have a Rename My TV Series. It uses the TVDB also when generating name for my files., It is not functioning, wont connect to TVDB, Because they both don’t work. I believe its on the TVDB side. Just my observation.

1 Like

(https://forums.thetvdb.com/viewtopic.php?p=168202&sid=24b7db3ab44e559c2a6e6677e853d3e4#p168202)

I found this post
[ Thu Jan 09, 2020 1:33 pm]

Dear Users,

As you probably know, we cutover to a new infrastructure, API, and website in early November 2019 and with that update came the introduction of some modern security features. However, as with any update, the transition revealed some upgrades we needed to make and we have made the tough decision to stop supporting a feature which may require some legacy users of the site to update their media centers. One issue that we encountered was that some older versions of Python (mostly 2.7) experienced issues due to a bug in their bundled url libraries. This caused some old scrapers and players to experience a SSL handshake failure due to outdated/unsupported TLS support. We put a temporary fix in place to remedy the issue and worked with some partners to put in a fix for their users, but our temporary solution is hugely expensive and presents a security issue for the site, the integrity of the data, and our users. Ultimately, we can no longer sustain this support and will be sunsetting our temporary fix soon. It may be in your best interest to reach out to the developers of your specific media center software to see if your system will be affected and if there are any upgrades that will solve this issue. We are sorry to discontinue the support of any technology that our users have become reliant upon, but this transition has made apparent that deprecating some of our older systems and early APIs is the only way we can continue to grow and build the best that TheTVDB has to offer.

Sincerely,
TheTVDB Team

I already linked that above in my OP !

Same problem , i was importing my TV Series last night. Alot Series fails to download any metadata at all.

I checked the TVDB log files and almost every request seems to get HTTPERROR 504 and sometimes 502.

For example:

2020-01-10 13:59:40,207 (7f2a0ffff700) :  DEBUG (networking:143) - Requesting 'https://tvdb2.plex.tv/search/series?name=Marvel%27s+Daredevil'
2020-01-10 13:59:40,455 (7f29df7fe700) :  ERROR (networking:196) - Error opening URL 'https://tvdb2.plex.tv/episodes/10722?lang=nl'
2020-01-10 13:59:40,456 (7f29df7fe700) :  INFO (__init__:162) - HTTPError 504:
2020-01-10 13:59:40,456 (7f29df7fe700) :  INFO (__init__:944) - Bad episode data, no update for TVDB id: 10722 (lang: nl)

I hope they fix this problem fast, because i migrated my server last night so this is not the perfect timing. :stuck_out_tongue:

Where do you get the 404 error from?
Putting the URL you cited above into your web browser will inevitably get the 404.
Or does the 404 appear in your server logs?

The SSL cutoff at ThetVDB is known and countermeasures are in development. There is also contact with the ppl at TheTVDB, and according to them the cutoff hasn’t been done, yet.

I have the same issue and I’m 95% sure it’s theTVDB removing their legacy ‘workarounds’ from their API. I also use TV Rename (2.9.9) and this also fails to download metadata from theTVDB too with I would imagine the same issue.

That post from theTVDB puts the fix firmly in Plex’s court now.

@OttoKerner the 404 error is from the console logs on the plex server

as does Filebot - she stopped negotiating with TVDB about 12 hours ago… I have raised an alarm at Filebot.net, just in case this isn’t just one of TVDB’s ‘outages’ that will heal if we quit picking at it.

4 Likes

The Horror!

That’s 3 Naming Maidens down - the implications are gonna be staggering… :astonished:

(let us pray - this is just temporary)

1 Like

Glad I’m not alone or going crazy. Starting having issues last night adding new TV series and thought maybe it was just a temporary API downtime so I tried again this morning and same thing still. When adding a new series it takes a really long time and eventually gives up with no match. Trying to do a manual Match fails as well, even when putting the ID in instead of name which usually should be a quick and immediate match.

Of course this would happen when I’m just beginning to convert my ASS/HAMA anime library over to a regular TV show library (using default Plex TheTVDB metadata agent instead)! It was working great yesterday afternoon and then went to have supper and put kids to bed and when I came back to resume moving some series over, suddenly nothing is matching!

Same problem here.,

This just in:

https://www.filebot.net/forums/viewtopic.php?f=6&t=11417&p=47938#p47937
and this:
https://www.filebot.net/forums/viewtopic.php?f=10&p=47939#p47939

Good things come (eventually) to those who wait.

@JuiceWSA I’m still waiting and its still failing :slight_smile:

Yea, me too…

I’ve abandoned Plex/Filebot/TVDB in favor of Company of Hereos 2.
That seems to be unaffected by these stressful (temporary) issues…
(When ur Plex Server is ur Gaming Rig - it’s easy to change gears)

:smiley:

1 Like

Same issue. Why is are the Plex developers not on this???

They are.

I am referring to the Plex usage of the metadata, which most certainly is a Plex issue. A big one.