YAY! I updated tonight, and it’s finding, and naming all the shows it’s missed in the last 2 months!
Thanks!!
I also updated tonight. I could see it actually processing shows that it had missed before. But at least one show has 2 season in the server that are still not showing up. When I pull the en.zip using the url in the thetvdb link and then look in the xml files I can see that those seasons are described in it. but the server refuses to see the folder/files.
I had to manually add the folders to the general group (TV) then it was able to see them.
@ziggimon said:
In the next release we have moved back to shipping the .py files with python lib so that can never happen again. The compiled python files seemed like a smart idea at the time, but we didn’t foresee that some platforms would leave files behind. We are now a lesson wiser and a fix richer.
I don’t do much with python, but doesn’t it automatically generate .pyc files when a script runs?
I was debugging this issue a few weeks ago, I deleted ssl.pyc, added some logging to ssl.py, restarted, and it generated a new .pyc file. My logging worked as expected.
In theory couldn’t you ship .py files but still take advantage of .pyc files?
Hmm … I tried 1.4.2 today and it is still not working 
It seems to not return any results when trying to match manually, too.
The error in the log is as follows:
Feb 24, 2017 23:55:48.412 [0x80d42b000] DEBUG - HTTP 401 response from GET http://127.0.0.1:32400/system/agents/update?mediaType=4&force=1&parentGUID=local%3A%2F%2F66446&parentID=66446&guid=local%3A%2F%2F66456&id=66456&agent=com.plexapp.agents.localmedia&async=0 Feb 24, 2017 23:55:48.412 [0x80d42b000] ERROR - Error response for update: ().
I already removed my PIN, restarted plex, reinstalled, deleted cache, deleted ssl.py and upgraded to 1.4.2 …
Help?
Edit: My apologies, messed up the list of topics 
This should have been posted in the Windows forum as a reply to this topic: https://forums.plex.tv/discussion/247645/metadata-not-downloading-in-full-if-at-all#latest. Can someone move it?
This problem (or at the very least, a closely related one) is still present in 1.4.2.
I upgraded yesterday from 1.2.7 (to which I reverted a couple times as it was the “latest” version that never exhibited this issue for me) and again Plex appeared to be unable to load information from TheTVDB.
tl;dr: It appears that somehow the certificate for *.plex.tv is not accepted as a valid certificate by Python on my Windows Server 2012 machine. Manually “trusting” the certificate solved all my issues.
More details: When trying to refresh a show (Sleepy Hollow in this case) using 1.4.2 from Plex Web, the following is reported in com.plexapp.agents.thetvdb.log:
2017-02-25 13:08:27,584 (f8c) : DEBUG (networking:166) - Requesting 'https://tvdb2.plex.tv/login'
2017-02-25 13:08:27,615 (f8c) : INFO (logkit:16) - JWT Error: (<urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)>) -
2017-02-25 13:08:27,631 (f8c) : DEBUG (networking:166) - Requesting 'https://tvdb2.plex.tv/series/269578/images?lang=en'
2017-02-25 13:08:27,645 (f8c) : INFO (logkit:16) - Problem with the request:
2017-02-25 13:08:27,645 (f8c) : INFO (logkit:16) - Bad image type data for TVDB id: 269578
Throwing the “JWT” error-message in Google yields a lot of generic Python/SSL related issues, amongst them this post on Stack Overflow: http://stackoverflow.com/questions/30704894/why-i-receive-certificate-verify-failed-from-google-adwords-api
This go me thinking it might actually be related to a broken trust-chain on the Windows Server 2012 machine I have running Plex. So, I downloaded the SSL certificate from https://tvdb2.plex.tv (which is the certificate for *.plex.tv, so it doesn’t matter which domain you get it from) and added it to the certificate store on my server.
Et voila, TheTVDB agent again works flawlessly.
For those interested in the workaround: You can easily download the SSL-certificate from https://tvdb2.plex.tv using Firefox (with Chrome not so easy). Instructions on how to add a certificate to your Windows’ certificate store are here.
@treboR2Robert said:
Yes I was told to use rsync too but all the code scarred me lol. I wasn’t expecting the 24 hour wait though with windows or I would have braved rsync.
I need to learn how to use freenas properly lol
I run Plex as a plugin in FreeNAS and found a simpler method of fixing it (rather than backing up and importing the DB into a new plugin jail).
Posting it here in case it helps someone else going through a lot of mucking around.
- Install an additional plugin for Plex using the FreeNAS web UI
- Turn off both old and new plugins via the FreeNAS web UI
- Log into your FreeNAS via SSH and run: sudo rsync -av /plexmediaserver_2/usr/pbi/plexmediaserver-amd64/share/plexmediaserver/ /plexmediaserver_1/usr/pbi/plexmediaserver-amd64/share/plexmediaserver/ (presuming plexmediaserver_1 is your original Plex jail name and plexmediaserver_2 is the new one)
- Start up the original Plex plugin via FreeNAS web UI
- Refresh TV library and watch as your precious metadata flows into place
- Delete the new Plex plugin as it is no longer required
This will replace any files in the old jail’s version of the /usr/pbi/plexmediaserver-amd64/share/plexmediaserver/ directory with those from the newly installed jail, and clear out any files that don’t belong in there (this is the key part).
Same issue here half my shows aren’t getting any metadata and I had one show that did and then suddenly lost it? this issue has become a thorn in my side since December, and hasn’t been resolved yet! At first TMDB was working with my tv shows just fine, now both aren’t working at all!!! I have been told by community helpers that I am to blame at least that’s how it sounded to me about this issue. I am running off a USB external drive if this is my fault then tell me how the crap the metadata issue wasn’t an issue until early to mid December 2017?!? It is now July 25, 2018 and this crap is still going on???
