You may notice a failure to fetch metadata for new media if you are using TVDB as an agent. This is due to TVDB changing their API to v3. Please see this post on their forums for further details.
4 Likes
Thanks for the update. So Plex needs an update to work with the new API?
We’ve made contact with many add-on developers, including PLEX with hopes to upgrade to TLS.
3 Likes
Thanks, I was just looking for a solution to my metadata problem, and I guess this is it.
But will solving this issue require an update for our servers? I’m on a fixed server version right now because of an unresolved issue, so I hope it can be fixed on your (or their) end.
That implies that Plex is forcing SSL 3.0 for any “secure” connections. Is that the case? If so, that’s kind of concerning since it’s been known to be broken for about 5 years now and Chrome, Firefox, and even Microsoft removed browser support for it in late 2014 or early 2015.
Please don’t get bogged down in speculating SSL v3 noise - not relevant.
There are two underlying changes with the TVDB agent
- The actual API call which is the primary change. The structure and arguments changed.
- How API errors show up in the log.
I worked with two of the team yesterday.
The invocation to TVDB went out as a “Connect & Request” as a single statement.
When the Request failed, it reported as “Connect” fail.
The resolution to this will be a change in the TVDB agent.
1 Like
Just to provide a little more detail, if you look in the logs you’ll see errors like this:
2019-11-16 11:35:48,246 (1670) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/_cache/posters/74205-14.jpg'
2019-11-16 11:35:48,315 (440) : ERROR (networking:219) - Error opening URL 'https://thetvdb.com/banners/_cache/posters/74205-5.jpg'
2019-11-16 11:35:48,315 (440) : INFO (logkit:16) - HTTP Error 403: Forbidden
2019-11-16 11:35:48,365 (440) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/_cache/posters/74205-12.jpg'
2019-11-16 11:35:48,387 (394) : ERROR (networking:219) - Error opening URL 'https://thetvdb.com/banners/_cache/posters/74205-8.jpg'
2019-11-16 11:35:48,387 (394) : INFO (logkit:16) - HTTP Error 403: Forbidden
2019-11-16 11:35:48,427 (394) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/_cache/posters/74205-15.jpg'
2019-11-16 11:35:48,460 (c58) : ERROR (networking:219) - Error opening URL 'https://thetvdb.com/banners/_cache/fanart/original/5c44e65a56b53.jpg'
2019-11-16 11:35:48,509 (c58) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/_cache/fanart/original/5d2fb1decbed4.jpg'
2019-11-16 11:35:48,530 (ce8) : ERROR (networking:219) - Error opening URL 'https://thetvdb.com/banners/_cache/posters/74205-13.jpg'
2019-11-16 11:35:48,532 (ce8) : INFO (logkit:16) - HTTP Error 403: Forbidden
2019-11-16 11:35:48,589 (1670) : ERROR (networking:219) - Error opening URL 'https://thetvdb.com/banners/_cache/posters/74205-14.jpg'
2019-11-16 11:35:48,589 (1670) : INFO (logkit:16) - HTTP Error 403: Forbidden
2019-11-16 11:35:48,611 (ce8) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/_cache/posters/5b0fde70b35c8.jpg'
2019-11-16 11:35:48,706 (440) : ERROR (networking:219) - Error opening URL 'https://thetvdb.com/banners/_cache/posters/74205-12.jpg'
2019-11-16 11:35:48,706 (440) : INFO (logkit:16) - HTTP Error 403: Forbidden
According to @ChuckPa it sounds like fixing these requires changes to the agent.
I just rebuilt my server so I’m missing metadata for all TV shows. I tried switching to the Movie Database, but it doesn’t seem to pick anything up either.
Correct: “403 - Forbidden” is a “No soup for you” when requesting a URL location.
Same as “Permission Denied” when attempting to open files.
Looks like I used the wrong search terms and why you closed my thread on this problem. Glad I’m not the only one dealing with this.
Curious as to why it does work on my shield PMS though?
If you are referring to the server running on the Shield, it should be the same behavior because the agent is the exact same but I will add that info to the bug report.
Yes, the shield server does find the metadata and art work.
@ChuckPa
Never mind on the shield. Just allowed the shield to up date to 1.18.2.2031 and it too no longer works. Was running 1.18.1.1973 previous to update.
On edit:
I just reinstalled 1.18.0.1846 on my synology and scraping thetvdb is working.
Is your bug tracker public? Any way to subscribe or get notified when it’s resolved so I can force a metadata refresh?
Nope, but do subscribe to:
1 Like
This “sticky” would probably suit better on the home page for the forum. It’s missed too easily, when you have to go to General >> General Discussions to find it
If I was looking for TVDB info not matching , I’d probably head off to Plex Media Server >>> Metadata & Adding Files as my first choice.
Just something to consider. 
2 Likes
Click on Latest.
1 Like
Converting to a “Notification” thread.
Future posts will be made by moderators and staff with updates.
Please continue discussion in the discussion thread linked below
2 Likes
There is a related discussion thread
1 Like
21.30 EDT - 17. Nov. 2019
Update
TheTVDB team, in conjunction with the Plex team, has been working over the weekend to restore metadata services.
At this time, everyone should see metadata flowing again into their systems.
It may be a bit before full service is restored but the API v3 rollout, which was to transparently include API v2 support, seems to be back on track.
15 Likes
