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

Apparently not as big an issue for some, as others.

I’m still getting TVDB metadata - if I name and structure my files (correctly), by hand, since Filebot is tapping it’s foot impatiently waiting for TVDB to come back up. <—and I am assured by it’s developer that will happen - when TVDB turns the lights back on.

1 Like

I don’t use Filebot; I manually title all media correctly, as per the Plex guide. It is still not pulling it correctly…

So… we wait then.

I have a WHOLE BUNCH of ‘horribly named items’ in a giant queue waiting for Filebot to work it’s magic. I did name and structure 12 episodes of “Watchmen The Motion Comic (2008)” (by hand) a while ago - 'cause they were ready to go - and all went well, except the naming and structuring by hand bit.

I can wait, and in a while, that giant queue of ‘horribly named items’ will be handled in seconds and the crisis will be over. For me.


I type fast, but, basically Filebot has made me a lazy, whimpering fool. I did manage the above and it worked, not instantly. <— 4 minutes. An eternity, but still not bad considering.

(episodes 06-12 are awaiting Xmedia Recode’s final touch-up, but… I’m busy)

6 and 7 just went in moments ago - and the expected happened:

I also just added this image for the ‘actor’ at both TVDB and TMDB - and when TVDB stops having ‘the shakes’ I’ll ask them to remove one of these guys - 'cause there’s two of them:

Of course, it’ll be at least 30 hours before we see this guy’s chiseled features on our Plex. <—if I could edit actors, I’d replace him with an image of Kermit the Frog. He’s way too pretty.

Note:
In 30 hours that will be an image of some eyeballs and a nose - when Plex’s Auto-Chop works it’s magic.

1 Like

Add me to the list of people not getting metadata updated. I won’t add the whole log, but here is part of it:

2020-01-10 14:11:54,881 (7fe77bfff700) :  ERROR (networking:196) - Error opening URL 'https://tvdb2.plex.tv/series/340489?lang=en'
2020-01-10 14:11:54,885 (7fe77bfff700) :  DEBUG (networking:143) - Requesting 'https://meta.plex.tv/tv/names/en/05/05c77e49f6a349a5f2d72739ecf59dfac5cffe9f.xml'
2020-01-10 14:11:55,019 (7fe77bfff700) :  DEBUG (networking:143) - Requesting 'https://meta.plex.tv/tv/names/en/57/571a71df7c992b63012423b896621cebec63cc0e.xml'
2020-01-10 14:11:55,210 (7fe77bfff700) :  ERROR (networking:196) - Error opening URL 'https://meta.plex.tv/tv/names/en/57/571a71df7c992b63012423b896621cebec63cc0e.xml'
2020-01-10 14:11:55,213 (7fe77bfff700) :  DEBUG (networking:143) - Requesting 'https://meta.plex.tv/tv/names/en/bf/bf426b2dadcbbc49473f2c8c6366529ded68c880.xml'
2020-01-10 14:11:55,404 (7fe77bfff700) :  ERROR (networking:196) - Error opening URL 'https://meta.plex.tv/tv/names/en/bf/bf426b2dadcbbc49473f2c8c6366529ded68c880.xml'
2020-01-10 14:11:55,411 (7fe77bfff700) :  INFO (__init__:369) - Searching for exact match with: XX+XXXXXX+XXXXXX (lang: en)
2020-01-10 14:11:55,411 (7fe77bfff700) :  DEBUG (networking:143) - Requesting 'https://tvdb2.plex.tv/login'
2020-01-10 14:12:10,132 (7fe77bfff700) :  ERROR (networking:196) - Error opening URL 'https://tvdb2.plex.tv/login'
2020-01-10 14:12:10,133 (7fe77bfff700) :  INFO (__init__:140) - JWT Error: (HTTP Error 502: Bad Gateway) - 
2020-01-10 14:12:10,133 (7fe77bfff700) :  DEBUG (networking:143) - Requesting 'https://tvdb2.plex.tv/search/series?name=XX+XXXXXX+XXXXXX'
2020-01-10 14:12:10,377 (7fe77bfff700) :  ERROR (networking:196) - Error opening URL 'https://tvdb2.plex.tv/search/series?name=XX+XXXXXX+XXXXXX'
2020-01-10 14:12:10,378 (7fe77bfff700) :  INFO (__init__:162) - HTTPError 401: 
2020-01-10 14:12:10,378 (7fe77bfff700) :  INFO (__init__:164) - Problem with authentication, trying again...
2020-01-10 14:12:10,379 (7fe77bfff700) :  DEBUG (networking:143) - Requesting 'https://tvdb2.plex.tv/login'
2020-01-10 14:12:15,276 (7fe77bfff700) :  ERROR (networking:196) - Error opening URL 'https://tvdb2.plex.tv/login'
2020-01-10 14:12:15,276 (7fe77bfff700) :  INFO (__init__:140) - JWT Error: (HTTP Error 502: Bad Gateway) - 
2020-01-10 14:12:15,279 (7fe77bfff700) :  DEBUG (networking:143) - Requesting 'https://tvdb2.plex.tv/search/series?name=XX+XXXXXX+XXXXXX'
2020-01-10 14:12:15,525 (7fe77bfff700) :  ERROR (networking:196) - Error opening URL 'https://tvdb2.plex.tv/search/series?name=XX+XXXXXX+XXXXXX'
2020-01-10 14:12:15,525 (7fe77bfff700) :  INFO (__init__:385) - There was a problem attempting an exact TVDB match in XX+XXXXXX+XXXXXX (lang: en)
2020-01-10 14:12:15,527 (7fe77bfff700) :  DEBUG (runtime:88) - Sending packed state data (607 bytes)
2020-01-10 14:12:15,527 (7fe77bfff700) :  DEBUG (runtime:924) - Response: [200] str, 320 bytes

Is there any official word from Plex about what is going on?

OMG…Again, WTF? Sounds like the same thing as before. Why haven’t the devs used this time to make sure PLEX works using updated SSL?

Funny tvdb says otherwise

“ 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. ”

Sonarr is working great for me.

So sonarr devs say it then it must be true. tvdb clearly states that they are no longer supporting outdated ssl protocol as of the exact same time we start having issues. that tells me our clients are trying to connect using unsupported ssl… no?

thanks, will check it out

Look, I see people pointing fingers at TVDB. At the end of the day, they can structure their API however they want. It is the responsibility of the services that utilize TVDB to make the appropriate changes to their platform.

TL;DR: Plex, get your act together!

2 Likes

True but not just Plex.
Also I don’t believe for a minute that Plex, Sonarr, Filebot etc…had no idea changes were coming.
That said TVDB also need to get their stuff together.
Earlier today there was an episode less in every season of Downton Abbey (sad I know) than there is now.
The show stopped existing. Then when it existed again every Christmas special suddenly became part of each season rather than part of Season 0/Specials.
I won’t even get started on documentaries. Now that really is a total shambles.

So is it TVDB suddenly changed API or Plex know and failed to update in due time, irresponsibly ?

TVDB reverted the API changes they made in November.

They’ve gone back to their old API

Plex needs to make an update to revert back to the old TVDB API.

Until then, Plex will have issues communicating with TVDB

Yeah I don’t think that’s what happened. They just removed the workaround they implemented when they changed their API in november, the one that allowed services like Plex to keep working.

3 Likes

No, they didn’t. (Yet)
The Plex devs are aware of the real cutoff date. I won’t divulge it here, I will just say that it lies still in the future, currently.

The current issues with TheTVDB are a different matter and have nothing to do with their removal of SSL protocol support.

Since Plex is operating their own proxy for TheTVDB data, it may need some time to download the backlog of all the updates it has missed during the outage of the original servers.

(It cannot download all data at once in one big rush, because that would have a similar effect on the tvdb as a denial of service attack.)

Looks to have sorted itself out overnight – thanks everyone for their comments and help investigating

It was a long night - waiting - but now all is well.
Filebot is working fine this morning - as is Plex and TVDB.

Ok thanks for the explanation. I read the post on their forum and thought that was the reason. Glad it’s working again. Let’s hope this one lasts.

So what whould I have to do to (re)load the data from TVDB?
I’ve tried “Refresh Metadata” on the episodes but still nothing…

EDIT:

I have a couple of

“ERROR (model:205) - Cannot read model from /share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server/Metadata/TV Shows…”

entrys in the com.plexapp.agents.thetvdb.log file but according to what I’ve found they don’t really matter, do they? I’ve checked on my QNAP and the file/folders are there and everyone has all the rights on them…

Try to clear the local agent cache: https://support.plex.tv/articles/202967376-clearing-plugin-channel-agent-http-caches/