OK, tearing my hair out here, because this is not making sense. Hoping someone can help.
I’ve been using Plex for over a year now with no problems and I love it. Recently I’ve rebuilt my server and suddenly Plex is refusing to download artwork for my TV Shows library. Its matching the shows correctly and getting the metadata, just no pictures. Movies and Albums have no such problems. I’ve gone through the help pages, tried adjusting the order of the Shows agents from the installed defaults but to no avail. Can’t see any obvious errors in the logs, but admittedly don’t really know what I’m looking for there. Nothings jumping out shouting “Error!” though.
Zip up your entire fleet of log files and we’ll see what’s up. There are some issue with the current version of PMS, but it’s not widespread as I don’t see it here - that doesn’t mean much other than anecdotal evidence.
Appreciate the point about naming conventions, but I have religiously followed the Plex rules since the start. And, as I said, its not that the tvdb agent isn’t matching anything; it is getting the metadata (see screenshot) just not the associated artwork.
Anyway since my first post I’ve dug into the logs a bit more and I think this in the com.plexapp.agents.thetvdb log might be the problem:
Variations of this message repeat through the log (see Logs.zip for the full story). Following this lead I have now picked up on some other threads in the forum (eg: https://forums.plex.tv/discussion/246749/tvdb-agent-ssl-certificate-verify-failed) where similar issues are being discussed. Some have had success with rolling back to PMS 1.2.7 and, after a bit of googling, I was able to find a website still hosting an Windows installer for that version (why don’t Plex host older releases on their own site?? :-?).
Uninstalled 1.3.3, tidy up leftover files/registry settings, reboot the server and installed 1.2.7. The tvdb agent downloaded both metadata and artwork.
As a further experiment/test, I then uninstalled 1.2.7 (again tidying up leftovers and rebooted) and reinstalled 1.3.3. The problem recurred. So I think there’s definitely an issue with the 1.3.3 release. Anyway it’s getting late (school night…), so I am going to wrap for now. Tomorrow evening I will revert to 1.2.7, load a couple of items into a TV Shows library and let it match, then upgrade to 1.3.3 and see what happens. It may be that this issue is only triggered by a clean installation which might explain why it doesn’t appear to be widespread. Otherwise I’ll be sticking with 1.2.7 for a bit!
The developers have been made aware of an issue with the current version. The ball is in their court. TVDB is also having major issues, so that’s not helping any. The issue doesn’t effect everyone and it comes and goes.
The good thing about updating regularly is you get the latest fixes - and you add another version to your archive (in your data directory). The bad thing is you get the latest bugs - but you have the last version in your archive. So on the one hand you can have the old bugs, or the new ones, but you just have to decide which ones cause the worst infectious wounds.
I’m still on 1.2.7, and haven’t upgraded due to the constant bug reporting. I did pay for a life pass. The whole point of Plex, is to have a whole media experience with a great user interface and presentation; your own “Netflix”, as it were.
So if the movie and show art is wrong; if the show episodes are out of order, etc, why use Plex? What is the advantage over DLNA, if you have a screwed up presentation package?
I’m not tech guru, and I’m sure many Plex users aren’t. All of us users… no, clients; want the most bug free experience possible. This is more important if you have shelled out money on a program. I do know that many users are non-paying, but when the thing that sets Plex apart from the basic, such as DLNA, seems to be broken, the paid up clients look like they may have paid an idiot tax.
The people behind Plex, have done a great job putting this system together, but it appears that there are some, what I, would call “major” bugs. Major, as they break the advantage Plex has… presentation and interface.
I’m sure the programmers are working on the issues which have been reported.
This is my opinion; I paid for a Life Pass, so I feel entitled to it. If anyone feels the need to “take the piss out of me”, don’t bother, as I will not reply to trolling.
The damage has been done. At this point all we can ask for is a follow up reply to acknowledge something will be done and another when the issue has been addressed. If the issue goes unanswered I will likely sit at this version for a long time (for the same reasons mentioned by Frank Logan) and eventually become apathetic and cease to promote the product and find something else. And that would be unfortunate considering the cumulative investment so far.
I am having the same issue. Its very frustrating. Besides rolling back the version has anyone find any fixes? Any word on an updated version to be released?
I am going to Roll forward my version to the latest again because I am sick of the web interface issues when using remotely. I have already tried the steps above and this was on a fresh install of Windows Server 2016 as a dedicated box. If the issue happens again I will post the screen shots but from what I have seen this is becoming a more common issue for windows 10+ users… should this be made into a bug ?
I am going to Roll forward my version to the latest again because I am sick of the web interface issues when using remotely. I have already tried the steps above and this was on a fresh install of Windows Server 2016 as a dedicated box. If the issue happens again I will post the screen shots but from what I have seen this is becoming a more common issue for windows 10+ users… should this be made into a bug ?
Thanks - but screenshots without all the logs is not going to help get the problem investigated. See my earlier post re logs
I have the logs and the screenshots. Please tell me exactly what log files you need from the ZIP and I will provide them. The issue is occurring again now I have updated to the latest version again.
sa2000 Please see PaulBambury post you have information you need to look into this problem, I still have yet to see anything that is pointing to a resolution to this problem.
@exilewolf said:
a fresh install of Windows Server 2016
I had already 2 similar issues with Server 2016. Apparently Microsoft disabled the automatic update of core certificates on there. Plex uses a relatively new certificate, which needs to be ‘trusted’. And on the newer Windows ‘Server’ editions this is only trusted if you:
import it manually into the Windows certificate locker
