TheTVDB V3 - Post grade issues

Plex Media Server Metadata & Adding Files
, ,
62

AFAIK, there is a scheduled call this afternoon.

This finding is fantastic thank you!

The team also agrees this is super fishy

63

OK…so, it is still not loading my posters. Here’s the latest log: Plex Media Server Logs_2019-11-20_10-44-28.zip (7.1 MB)

64

We found 2 TheTVDB hosts which are misbehaving.

We’re following up with them to resolve.

1 Like
65

Yes the 13.xxxx ip is the one that was not working.

I should also not that artworks.thetvdb.com is a cname pointing to d13gffiydmyxxy.cloudfront.net. Which is now back to the 13.xxx ip’s and not the 99.xxxxx I had this morning.

66

what we’re finding is there exist, in the pool of hosts, some of the older 13.x.x.x addresses.

There are a couple possible answers here:

  1. DNS didn’t update proper and push to all the other DNS servers

  2. Amazon Compute Services, which replicates and provides alternate DNS addresses per global region, didn’t update correctly.

  3. (more likely) Two of the hosts which make up the cluster need some attention.

67

It looks like the 143.xxx addresses are also not working sadly, I flushed my DNS and got new ips for the artworks.thetvdb.com and these are also not working:

;; ANSWER SECTION:
artworks.thetvdb.com.	5	IN	CNAME	d13gffiydmyxxy.cloudfront.net.
d13gffiydmyxxy.cloudfront.net. 1 IN	A	143.204.29.83
d13gffiydmyxxy.cloudfront.net. 1 IN	A	143.204.29.69
d13gffiydmyxxy.cloudfront.net. 1 IN	A	143.204.29.47
d13gffiydmyxxy.cloudfront.net. 1 IN	A	143.204.29.44

Hopefully this gets fixed by thetvdb soon!

68

FYI, using:

Non-authoritative answer:
Name: thetvdb.com
Address: 54.230.243.39
Name: thetvdb.com
Address: 54.230.243.43
Name: thetvdb.com
Address: 54.230.243.251
Name: thetvdb.com
Address: 54.230.243.120

These will be AWS in Aus.

69

Is there a status page we can check on to see when it’s fixed? Or is it just this post?

70

Hi Chuck,

now that I’ve got some time, I found the following: My TS-651 still is not matching posters. Turns out, my TS-251+ is matching them just fine. Same QTS 4.4.1.1117, now same PMS version 1.18.2.2049. One difference between those two is that the TS-651 has a Let’s Encrypt certificate + a myQNAPcloud address for it’s web server. I released the certificate for testing purposes but still can’t get a match with a poster. If you need more information to pin this down, let me know.

BR,

Alex

71

I’m not getting any artworks for the newly added shows and episodes.
I did a full refresh after cleaning out the cache as read in a post at the very top.

Here are my logs;
Plex Media Server Logs_2019-11-21_02-09-08.zip (6.1 MB)

72

I’m still not getting artwork for shows, seasons, and episodes.
I’ve cleaned the cache and done a full refresh.

Logs:
Plex Media Server Logs_2019-11-20_17-02-58.zip (921.1 KB)

73

Folks

There is no need to post or notify us it’s still not working.

We are well aware of what’s happening and are working with the team from TheTVDB to resolve it. This problem is, unfortunately, on their side of the service to repair. we must unfortunately wait.

4 Likes
74

Hi @ChuckPa, I have found/fixed an issue with Plex’s “HTTP.Request()” function not working with “api.thetvdb.com”. This is on Plex’s end of not being able to handle SNI. Please advise how you would like me to send the details as you are not open to direct messages through the forums.

2 Likes
75

Sent.
I am curious what you found because the version we use has SNI support.

76

@EndOfLine369 I’m curious also. SNI is certainly part of the TLS handshake process, and the handshake is what’s showing in the logs as what’s failing. That might also explain why other services I use that also use thetvdb like Sonarr hasn’t had any issues this whole time. I’ve been really curious how that could be, maybe plex’s handling of SNI is involved?

1 Like
77

I fail to see how this specific problem is the fault of TheTVDB:

DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/fanart/original/5dadd3787d15d_t.jpg'
INFO (__init__:1079) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>

Testing the same URL with TLSv1.0 and upwards works with curl:

curl --tlsv1.0 https://thetvdb.com/banners/fanart/original/5dadd3787d15d_t.jpg

Testing the same URL with SSLv3 does not work:

curl --sslv3 https://thetvdb.com/banners/fanart/original/5dadd3787d15d_t.jpg

curl: (35) gnutls_handshake() failed: Handshake failed

Plex is trying to use SSLv3, which is not supported by TheTVDB and needs to be fixed by Plex because it’s 2019 and SSLv3 has been deprecated since 2015. So this would be a nice time to upgrade to TLSv1.2.

4 Likes
78

Everyone please breathe.

I’ve been working all evening on this.

Examination of the message (which isn’t SSLv3 – it’s TLS 1.2 protocol-- only the decades-old library is saying SSLv3) was misleading.

I will be able to update tomorrow after my testing completes.

G’night all. 03.20a here.

10 Likes
79

Yeah that’s what a lot of people have been saying from the beginning. Everything grabs meta/posters from thetvdb.com fine except Plex… yet everyone is saying it isn’t Plex’s issue.

80

This should be it:
https://forums.thetvdb.com/viewtopic.php?f=122&t=60239

3 Likes
81

Saw this reply from a Plex employee on Reddit. Fix will require a PMS update. “what happened is that TVDB updated their SSL ciphers and we had a very old version of SSL support in the agents specifically.”