No Metadata or posters for TV shows (error INFO (__init__:140) - JWT Error: (<urlopen error (574: The handshake operation timed out',)

Hi,
Since a couple of days non of my Plex servers (2) both on Version 1.13.3.5223
are not downloading any Metadata or Posters for my TV Shows.
i already removed and re-added the Library, same results.
Clearing the Cache did also not helped/

running it on lilnix plex version 1.13.3.5223
same issue on 2 different servers. also on a new installation.
however same version on windows is working.

please find attached my log files.

Plex Media Server Logs_2018-07-05_17-47-35.zip (6.1 MB)

Same issue, all 11 plex servers not downloading TV Show data. I’m assuming this is a TVDB issue at first; I believe Version 1.13.3.5223 was supposed to fix the changes TVDB made according to a few forum threads. Kind of a pain right now

ok, that would explain why its not working on any of my linux servers, even on a new installation.
but why is it then working on a new installation of PMS 1.13.3.5223 on windows?
is it fixed for windows already but not for the linux version

Nope. Mostly windows user here and definitely not working.

The only way I can get any artwork to show is using a sideloader and putting the banners/posters in the root TV Show folder.

ok, now its getting strange. i installed it earlier today on windows 10 and it worked just fine :face_with_raised_eyebrow:

What did you use for your agents?

EDIT: right now I’m starting to use a sonar plugin to download the art and use local media inside plex

Okay screw the built in plex artwork downloaders. Use Media Center Master to download all that stuff for you and just set as local. Just downloaded everything for 4500 tv shows in about 10 mins and I’m back up and running smoothly

i actually used the tvdb agent, that’s why i’m so surprised that i got any metadata.
was also thinking of using the sonarr plugin as well.

May I see some log files please?

  1. Attempt metadata download (force)
  2. After a few fail, Collect the ZIP of all logs (Settings - Server - Help - Download Logs)
  3. Attach ZIP please

@ChuckPa

please find attached the log files.
Plex Media Server Logs_2018-07-09_02-06-36.zip (1.9 MB)

the vast majority of what I’m seeing is because the database is fragmented.

Jul 09, 2018 01:58:22.531 [0x14b7363c6700] WARN - SLOW QUERY: It took 260.000000 ms to retrieve 66 items.
Jul 09, 2018 01:58:22.536 [0x14b7311fe700] DEBUG - It took 320.000000 ms to retrieve 110 items.

Manually optimize the DB.
Stop PMS
Clear the contents under (Plug-in Support/Caches/*)
Start PMS

Not related to this but PMS has a finite list of agents which can run at any one time. Start turning on others turns off what’s needed.

Local Media Assets does just fine in finding properly named content (including posters / cover art) when properly named and the Agent is enabled

hi, will look into that. but that would not explain why i have the same behavior with a fresh installation.

Why optimize the DB during a fresh install? All that new data is coming in and the butler hasn’t run yet. The DB is an indexed SQLITE3 (single file) database. Tables get fragmented all over the place. When that happens, query time takes longer. At a certain point, the agent gives up waiting and starts looking elsewhere.

That whole mechanism is being rewritten now by engineering. The issues we’re seeing will be gone.

what i’m trying to say is, that the initial problem with not getting any metadata for my TV shows seems not to be linked to the database. because if i setup a fresh installation of plex, im facing exactly the same problem of not getting any metadata.

Are you 100% certain it’s not naming, structure, or embedded metadata in AVI/MP4 files? In 99% of the cases I see, that’s precisely the problem.

Naming and structure means:

Movies get: Name (year)/Name (year).ext
Episodes get: Series/Season s/Series - SxxExx - optional title.ext

Sorry, but i forgot to post this part of the initial complaint

2018-07-05 15:34:35,849 (14c282a45700) :  DEBUG (networking:166) - Requesting 'https://tvdb2.plex.tv/login'
2018-07-05 15:34:54,527 (14c282f87700) :  INFO (__init__:140) - JWT Error: (<urlopen error ('_ssl.c:574: The handshake operation timed out',)>) - 
2018-07-05 15:34:54,545 (14c282f87700) :  DEBUG (networking:166) - Requesting 'https://tvdb2.plex.tv/series/284210?lang=en'
2018-07-05 15:34:54,900 (14c282084700) :  INFO (__init__:140) - JWT Error: (<urlopen error ('_ssl.c:574: The handshake operation timed out',)>) - 
2018-07-05 15:34:54,913 (14c282084700) :  DEBUG (networking:166) - Requesting 'https://tvdb2.plex.tv/series/255316?lang=en'
2018-07-05 15:34:55,958 (14c282a45700) :  INFO (__init__:140) - JWT Error: (<urlopen error ('_ssl.c:574: The handshake operation timed out',)>) - 
2018-07-05 15:34:55,973 (14c282a45700) :  DEBUG (networking:166) - Requesting 'https://tvdb2.plex.tv/series/263365?lang=en'

What’s in between PMS and the server? A VM? A container? SSL.c tells me either a proxy or firewall or something else is preventing the SSL connection to connect to GET the data

1 Like

actually i have this one running in an docker container on unRaid.
another one, where i have the same problem with, log files have the same SSL error, is running on a linux server in a VM.

Ok. That explains it. The best I can do is to move you to the Docker forum.
I don’t use docker nor can I keep up with all the nuances of it so I let that team handle it.

Would you mind if I moved this thread to the docker forum (tag) ?

1 Like

Something isn’t right here. The more I think about this case, I keep asking “what’s the common element?”

Host? Do both run on the same host?
Network? Two different hosts on the same subnet or different behind the same router/firewall ?

See my thinking? What’s different that causes you this problem but not seen by others.

both are on the same network but on different hosts.
all behind the same router, which was not changed since long time.

i totally see what you want to say, i looked into this as well but since nothing changed, except the update of plex itself, i could not find any explanation for this problem, the ssl error.