For me it is https://www.thetvdb.com/series/war-of-the-worlds-2019
Been through the suggestions above to clear the plugins cache but still having issues with artwork downloading; this appears to be for new shows which were added to plex during the issues with TVDB.
Logs attached. I have tried Refresh Metadata, and Fix Match.
From the com.plexapp.agents.thetvdb.log log I can see a number of artwork download errors as follows:
2019-11-20 07:52:21,265 (14d333fff700) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/seasons/84912-1-2_t.jpg'
2019-11-20 07:52:21,294 (14d37072b700) : INFO (__init__:1079) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>
However the URL being opened will open in my browser (firefox).
Plex Media Server Logs_2019-11-20_07-52-59.zip (1.8 MB)
Background:
Server: HP MicroServer Gen8
Base OS: unRaid 6.7.2
Plex: 1.18.2.2041 running in LSIO Docker
Client: Windows 10 / Firefox
Location: UK
@ChuckPa as we discussed, I just did a precise side-by-side comparison of PMS 1.18.1.1973 (~3wks old) and PMS 1.18.2.2029 (~1wk old) on the same machine (a raspberry pi 4b fwiw) using literally the exact same files for its configs (a common folder both installs were pointed at).
TL;DR: With literally everything I could think of identical between the two installs, except the Plex version, and the Show being added, both installs exhibited the same behavior - the text metadata and cast headshots pulled successfully, but not the show posters/banners, etc. Here’s the full detail:
Methodology:
- With Plex running, I removed all content so there would be no libraries of any kind, then stopped plex
- With Plex stopped, I deleted all files in
- Library/Application Support/Plex Media Server/Cache
- Library/Application Support/Plex Media Server/Plug-in Support/Caches
- Library/Application Support/Plex Media Server/Logs
PMS version 1.18.1.1973
- I started plex (ie: a docker container w/ PMS version 1.18.1.1973 in it)
- With plex running, I added a tv show folder with just one show in it (Adam Ruins Everything)
- Plex successfully pulled textual metadata and cast headshots, but not any other kind of visual metadata like posters
- Refreshing metadata failed to produce different results, whether for an entire show, or just 1ep
- I confirmed thetvdb logs contained lines seen previously like:
2019-11-20 07:04:13,874 (-4f601ba0) : DEBUG (threadkit:234) - Starting a parallel task set named DownloadImages with 10 tasks
2019-11-20 07:04:13,879 (-50603ba0) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/fanart/original/300774-1_t.jpg'
2019-11-20 07:04:13,894 (-50e44ba0) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/fanart/original/5c056e0e7a802_t.jpg'
2019-11-20 07:04:13,899 (-51645ba0) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/fanart/original/300774-2_t.jpg'
2019-11-20 07:04:13,903 (-51e46ba0) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/posters/300774-1_t.jpg'
2019-11-20 07:04:13,908 (-50603ba0) : INFO (__init__:1064) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>
2019-11-20 07:04:13,927 (-50603ba0) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/posters/300774-2_t.jpg'
2019-11-20 07:04:13,929 (-51e46ba0) : INFO (__init__:1068) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>
2019-11-20 07:04:13,932 (-51e46ba0) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/posters/300774-3_t.jpg'
2019-11-20 07:04:13,935 (-50e44ba0) : INFO (__init__:1064) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>
2019-11-20 07:04:13,940 (-50e44ba0) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/posters/300774-4_t.jpg'
2019-11-20 07:04:13,945 (-51645ba0) : INFO (__init__:1064) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>
2019-11-20 07:04:13,952 (-51645ba0) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/posters/300774-5_t.jpg'
- I then deleted all libraries, and shut down plex
- With Plex stopped, I deleted all files again in
- Library/Application Support/Plex Media Server/Cache
- Library/Application Support/Plex Media Server/Plug-in Support/Caches
- Library/Application Support/Plex Media Server/Logs
PMS version 1.18.1.1973
- I then started plex (ie: a docker container w/ PMS version 1.18.2.2029 in it)
- With plex running, I added a folder with a DIFFERENT tv show in it than before (Carnival Row)
- Again, plex successfully pulled textual metadata and cast headshots, but not any other kind of visual metadata like posters
- Refreshing metadata failed to produce different results, whether for an entire show, or just one episode
I hope this is helpful to you. Took about an hour all tolled.
Update: A bit more testing further confirming the symptoms described above. That is - my old faithful install of PMS that’s been used heavily every day for 3 years, running on an old macbook pro - I just tested metadata pulling from it on an older version then the latest beta. Specifically, I started on Version 1.18.1.1966, and navigated to Saturday Night Live, Season 45. I noticed in there that all older episodes before S45E06 had correct fanart matching https://thetvdb.com/series/saturday-night-live/seasons/official/45. However, the most recent episode (S45E06 - Harry Styles was host) - did not. That Harry Styles episode aired last weekend, and these metadata issues have persisted for me since before then, thus, that episode’s artwork was pulled from the file itself, and didn’t match that thetvdb fanart. So, I attempted one more metadataupdate on that older PMS Version Version 1.18.1.1966, then I updated it to 1.18.2.2041, shut it down, cleared the plugin support caches folder, started it up, and… no change - still the same ssl handshake error, and no change to its ability to pull the correct fanart. HTH
Have been through cache clearing process etc and still seeing issues, basically same SSL handshake error error as others, tv series in question was Ray Donovan
2019-11-20 18:24:39,213 (15548a337700) : DEBUG (networking:166) - Requesting ‘https://thetvdb.com/banners/posters/259866-7_t.jpg’
2019-11-20 18:24:44,292 (15548a337700) : INFO (init:1063) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>
setup is binhex-plexpass docker running on unraid
im no expert but isnt this because the remote server (tvdb) requests cipher that isn’t supported by the OS/app ? have TVDB made updates to SSL config at their end ?
So for my test. I signed my test server out of my Primary Plex Pass account and re claimed the server under a second free Plex account.
So it is now just a standard Server install with no custom certs or anything like that.
Removed this account from my Sharing from my Primary account.
Just one TV Library with a couple of episodes of just one season
Still seeing the same thing, no Posters for Show or Season, and the SSL Errors in the log files
fwiw the Show was Homeland, so not a new show.
Shows for me are “See”, “Godfather of Harlem” and “The Mandalorian” - all added in the past week or so. Episode thumbnails haven’t been downloading either for about the same time.
I won’t bother adding logs as they contain the same “[SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure” errors as everyone else, but I can confirm a similar situation as the user audiomixer earlier in the thread.
On my Synology server I’m getting the SSLV3 errors, but on my Windows server I’m pulling through posters fine. The media on both servers is identical as I only setup the Synology yesterday and did a straight copy and paste between my drives.
I’ve tried removing and readding the media to both servers and confirmed that only the server running on Synology is affected. Hope that helps.
Here is my log
this kind of confirms my thoughts there is a SSL change of some kind at TVDB end, windows handles the handshake error differently and still allows the request to pass however in our cases NAS OS’s (me Unraid, you Synology) arent as tolerant and not allowing the requests.
RC4-MD5 no longer supported ?
@ChuckPa I’ve just done a fresh install on Ubuntu Server 18.04 with Plex pass version 1.18.2.2041-3d469cb32 (Ubuntu /16.04+( /Deban (8+) - Intel/AMD 64-bit)
(I also cleared all cache, and then refreshed metadata.)
My movies posters download fine. TVShows does not. If I change the agent to TMDB then posters still does not get downloaded.
In the log file: com.plexapp.agents.thetvdb.log I also see SSL errors errors:
2019-11-20 13:14:09,790 (7f23d8ff9700) : DEBUG (threadkit:234) - Starting a parallel task set named DownloadImages with 2 tasks
2019-11-20 13:14:09,792 (7f23bade2700) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/fanart/original/5d75ded4566e8_t.jpg'
2019-11-20 13:14:09,793 (7f23d97fa700) : DEBUG (networking:166) - Requesting 'https://thetvdb.com/banners/graphical/5d75e23062b5a_t.jpg'
2019-11-20 13:14:09,881 (7f23bade2700) : INFO (__init__:1073) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>
2019-11-20 13:14:09,895 (7f23d97fa700) : INFO (__init__:1079) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>
2019-11-20 13:14:09,896 (7f23d8ff9700) : DEBUG (threadkit:244) - Parallel task set DownloadImages ended
If I take one of the links and download with curl if works fine however:
root@zeroz:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs/PMS Plugin Logs# cd
root@zeroz:~# curl -vvv https://thetvdb.com/banners/fanart/original/5d75ded4566e8_t.jpg --output test
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 13.33.62.179...
* TCP_NODELAY set
* Connected to thetvdb.com (13.33.62.179) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [70 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [4874 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=*.thetvdb.com
* start date: May 23 00:00:00 2019 GMT
* expire date: Jun 23 12:00:00 2020 GMT
* subjectAltName: host "thetvdb.com" matched cert's "thetvdb.com"
* issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0x56504e9df580)
} [5 bytes data]
> GET /banners/fanart/original/5d75ded4566e8_t.jpg HTTP/2
> Host: thetvdb.com
> User-Agent: curl/7.58.0
> Accept: */*
>
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
} [5 bytes data]
< HTTP/2 200
< content-type: image/jpeg
< content-length: 32001
< date: Wed, 20 Nov 2019 11:40:59 GMT
< last-modified: Wed, 16 Oct 2019 02:43:39 GMT
< etag: "c82bfd318b4a17304fad1d3e706d76c5"
< accept-ranges: bytes
< server: AmazonS3
< x-cache: Hit from cloudfront
< via: 1.1 4565946be0cd8151bce94cfc74bc1c00.cloudfront.net (CloudFront)
< x-amz-cf-pop: ARN54
< x-amz-cf-id: U7hgwv6bPdhwPrWEpsyaruuD4NC7xt5BPipjqiUDWKi7djonD2yp2w==
< age: 2086
<
{ [16060 bytes data]
100 32001 100 32001 0 0 153k 0 --:--:-- --:--:-- --:--:-- 153k
* Connection #0 to host thetvdb.com left intact
root@zeroz:~#
Which makes me think the previous person saying Plex Media Server is using old libraries not compatible with SSL is right. Maybe a new Plex update needs to be pushed to address this? And do you know of any temporary fix that can be done?
I have cleared the cache as suggested, but I am still not getting posters for my TV shows.
Plex Media Server Logs_2019-11-20_06-55-01.zip (526.6 KB)
I tried downgrading to 1.15.8 and I’m still getting the same issues. Show details are imported but posters are not.
Stopped PMS, cleared the Caches (actually moved them aside & recreated the directory, in case a comparison is needed), started PMS again and ran a Refresh All Metadata task, checked if the missing poster was there and then gathered the server logs. Looking inside I see loads of:
INFO (init:1059) - <urlopen error [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:590)>
QTS: 4.4.1.1117 on a TS-651 with PMS 1.18.2.2041-3d469cb32
Find the logs attached: Plex Media Server Logs_2019-11-20_14-41-39.zip (4.4 MB)
HTH!
Alex
So, I cleared the cache and ran a refresh metadata on one section (my dvr shows). It restored all but one poster/metadata. The one show it couldn’t restore is an odd-duck kind of show so TVDB may not even have it listed. I’d consider this a successful test. I’ll now run it against my main 12TB library and see what happens, but that will take a day or so… I’l report back. Thanks for all the help!
Stopped server, cleared cache, restarted, no luck.
Logs attached: Plex Media Server Logs_2019-11-20_09-00-06.zip (1.2 MB)
Update: 20-Nov-2019
As recently as last night, there were conversations back & forth about the SSLv3 / TLS 1.1 which everyone is seeing.
It’s confirmed this is still an issue on TheTVDB side and still being worked.
3 Likes
I am having the same issue. I took a peek at the logs and I too am having the SSLv3 error.
Plex Media Server Logs_2019-11-20_07-52-11.zip (2.5 MB)
Correction I had the issue: Since this is an SSLv3 issue I decided to run a SSL test with https://www.ssllabs.com/ssltest on the site that the artwork downloads from (artworks.thetvdb.com). Since there are many servers for this site I needed to know what server my PMS was attempting to talk too. So I ping it and find that the IP returned was not in the list. Checking my local dns results same issue (all my systems are on AD). So run ipconfig /flushdns. Wait a few check the IP that resolves with ping and then refresh my metadata and voila, artwork downloaded.
Bottom line looks ,at least for my issue, the system was holding onto an old IP address for the artwork site that is no longer valid. I might suggest clearing your local dns caches as well.
edit: for completeness the IP address that was not working form thetvdb.com is 13.225.146.15
1 Like
Wait, I dont understand the last EDIT part. The IP address “13.xxxx” is that the one that didnt work for you or it did?
Currently I am checking the DNS addresses online and all 4 of them are telling me the same 13.xxx something IPs.
But on my linux machine, when I do a nslookup it shows this:
Non-authoritative answer:
Name: thetvdb.com
Address: 99.84.92.116
Name: thetvdb.com
Address: 99.84.92.7
Name: thetvdb.com
Address: 99.84.92.109
Name: thetvdb.com
Address: 99.84.92.40
I see a different block (as I should) because of Amazon.
Name: thetvdb.com
Address: 13.249.44.16
Name: thetvdb.com
Address: 13.249.44.109
Name: thetvdb.com
Address: 13.249.44.18
Name: thetvdb.com
Address: 13.249.44.47
Name: thetvdb.com
After 10 mins, those are the same addresses I have now… well, somethings still fishy there on TheTVDB 
